secret-scanning
Skill1 starsChanged 2 months agoMITView on GitHub
Scan codebase, git history, configuration files, and diffs to prevent accidental exposure of secrets and credentials.
- Reads credentials
7 other projects use a version of this.
Adopted by
Most recently taken up by
- kaandgnsh/Claude-Bluetheir own version, first seen Nov 1, 2026
- github/awesome-copilottheir own version, first seen Oct 25, 2026
- PracticalSwan/agent-skillstheir own version, first seen Oct 19, 2026
- valtterimelkko/agent-workflow-skillstheir own version, first seen Sep 30, 2026
- firstsun-dev/firstsun-bottheir own version, first seen Jul 22, 2026
- ReaperOAK/ForgeOStheir own version, first seen Jun 8, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- github/awesome-copilot★ 41ksame name
- PracticalSwan/agent-skills★ 22same name
- github/copilot-advanced-security-plugin★ 20same name
- valtterimelkko/agent-workflow-skills★ 2same name
- firstsun-dev/firstsun-bot★ 0same name
- kaandgnsh/Claude-Blue★ 0same name
- ReaperOAK/ForgeOS★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository55 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- accessibility-and-inclusive-designSkill
- animateSkill
- api-contracts-and-backward-compatSkill
- appsec-code-reviewSkill
- architecture-decision-recordsSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- concurrency-and-race-conditionsSkill
- database-and-migrations-architectSkill
- dependency-vulnerability-auditSkill
- design-taste-frontendSkill
- emil-design-engSkill
- graphifySkill
- headroomSkill
- impeccableSkill
- incremental-implementationSkill
- observability-and-structured-loggingSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- refactoring-legacy-codeSkill
- root-cause-analysis-and-postmortemSkill
- secret-scanningSkill
- shipping-and-launchSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- threat-modelingSkill
- accessibility-and-inclusive-designSkill
- animateSkill
- api-contracts-and-backward-compatSkill
- appsec-code-reviewSkill
- architecture-decision-recordsSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- concurrency-and-race-conditionsSkill
- database-and-migrations-architectSkill
- dependency-vulnerability-auditSkill
- design-taste-frontendSkill
- emil-design-engSkill
- graphifySkill
- headroomSkill
- impeccableSkill
- incremental-implementationSkill
- observability-and-structured-loggingSkill
- planning-and-task-breakdownSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- refactoring-legacy-codeSkill
- root-cause-analysis-and-postmortemSkill
- shipping-and-launchSkill
- spec-driven-developmentSkill
- test-driven-developmentSkill
- threat-modelingSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 18
Never commit plaintext secrets to Git repositories, even in private repos.
- Very specific: line 20
Ensure .gitignore explicitly excludes .env, .env.*.local, *.pem, *.key, *.pfx.
- Distinctive: line 21
If a secret is committed: Immediately rotate/revoke it.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Secret Scanning & Credential Protection
Zero tolerance for hardcoded credentials in source control:
1. Detection Signatures
- Cloud Credentials: AWS Access Keys (
AKIA...), Google Cloud service accounts, Azure client secrets. - API Tokens: GitHub PATs (
ghp_...), OpenAI/Anthropic/Stripe/Twilio API keys. - Cryptographic Keys: RSA/OpenSSH private keys (
-----BEGIN PRIVATE KEY-----), TLS certificates. - Connection Strings: Database URIs containing embedded passwords (
postgres://user:pass@host/db). - Sensitive Configs: Uncommitted
.envfiles, backup tokens, hardcoded JWT secrets.
2. Remediation Rules
- Never commit plaintext secrets to Git repositories, even in private repos.
- Store secrets strictly in environment variables or managed secrets stores (Vault, AWS Secrets Manager).
- Ensure
.gitignoreexplicitly excludes.env,.env.*.local,*.pem,*.key,*.pfx. - If a secret is committed: Immediately rotate/revoke it; do not assume deleting the commit in git is sufficient.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.