# secret-scanning-integration

> GitHub secret scanning configuration, push protection, custom pattern definitions, and response playbook for detected credentials in GitHub Actions workflows.

- Author: Mark Cheret
- Repository: adaptive-enforcement-lab/claude-skills
- Version: 20260105224107
- Stars: 0
- Forks: 0
- Last Updated: 2026-02-07
- Source: https://github.com/adaptive-enforcement-lab/claude-skills
- Web: https://mule.run/skillshub/@@adaptive-enforcement-lab/claude-skills~secret-scanning-integration:20260105224107

---

---
name: secret-scanning-integration
description: >-
  GitHub secret scanning configuration, push protection, custom pattern definitions, and response playbook for detected credentials in GitHub Actions workflows.
---

# Secret Scanning Integration

## When to Use This Skill

Prevention is good. Detection is essential. Assume secrets will leak. Build systems to catch them before damage spreads.

> **The Risk**
>
>
> Secrets leak through commits, workflow logs, artifacts, pull requests, and third-party integrations. Without automated scanning, credentials remain exposed for days or months before detection. By then, your infrastructure is already compromised.


## Implementation

See the full implementation guide in the [source documentation](https://adaptive-enforcement-lab.com/secure/github-actions-security/).


## Examples

See [examples.md](examples.md) for code examples.


## Full Reference

See [reference.md](reference.md) for complete documentation.
## References

- [Source Documentation](https://adaptive-enforcement-lab.com/secure/github-actions-security/)
- [AEL Secure](https://adaptive-enforcement-lab.com/secure/)