secret-scan
Skill1 starsChanged 45 days agoMITView on GitHub
Find secrets before they reach a commit. Use before running git commit, when reviewing staged changes, or when auditing a directory for API keys, tokens, passwords, and credentials. Findings are masked and never leave the machine.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- NexaiGuy/nex-ai-skillstheir own version, first seen Nov 8, 2026
- Vulnetix/pix-ai-coding-assistanttheir own version, first seen Nov 6, 2026
- matheuskotayko/skillstheir own version, first seen Nov 1, 2026
- Quality-Max/free-qa-skillstheir own version, first seen Oct 25, 2026
- PerryLink/dsh-skill-pack-securitytheir own version, first seen Aug 15, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- PerryLink/dsh-skill-pack-security★ 22same name
- Quality-Max/free-qa-skills★ 13same name
- Vulnetix/pix-ai-coding-assistant★ 9same name
- KhaledSaeed18/dotclaude★ 5same name
- kronus-tech/kronus★ 4same name
- NexaiGuy/nex-ai-skills★ 1same name
- matheuskotayko/skills★ 0same name
- vbrevik/claude_code_skills★ 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 repository9 other files it gives its agents.
- commitsmithSkill
- context-budgetSkill
- gatewaySkill
- injection-guardSkill
- json-lensSkill
- log-tailSkill
- repo-mapSkill
- tokensaverSkill
- web-snapshotSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 1 is distinctive, and 4 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 27
After git add, call scan_diff with staged: true.
- Very specific: line 28
Treat any critical or high finding as blocking.
- Very specific: line 29
Use scan_text for content that has not been written to disk yet.
- Very specific: line 30
Use allowlists for fixtures: inline secret-scan:ignore comments or .secretscanignore.
- Distinctive: line 43
Never paste a found secret into a message or issue — rotate it instead.
“Common” is measured: kept by at least 6 in 10 of the 6 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 scan
Scan staged diffs, files, and text for secrets — AWS, GitHub, OpenAI, Anthropic, Google, Slack, Stripe, npm, PyPI, SendGrid, Twilio, private keys, URI credentials, JWTs, generic assignments, and high-entropy strings. Output is masked; the full secret is never printed.
MCP tools
| Tool | Use it for |
scan_diff | The commit gate: scan staged or working-tree changes with exact file/line. |
scan_text | Check a snippet before writing it anywhere. |
scan_path | Audit a file or directory tree. |
Workflow
- After
git add, callscan_diffwithstaged: true. - Treat any
criticalorhighfinding as blocking; fix before committing. - Use
scan_textfor content that has not been written to disk yet. - Use allowlists for fixtures: inline
secret-scan:ignorecomments or.secretscanignore.
CLI fallback
npx -y mcp-secret-scan scan --staged
npx -y mcp-secret-scan scan ./src --strictExit code 1 blocks the commit; ideal as a pre-commit hook.
Tips
- Never paste a found secret into a message or issue — rotate it instead.
- Placeholders like
your_api_key_hereare ignored automatically to keep false positives low.
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.