secret-scanner
Skill1 starsChanged 5 months agoMITView on GitHub
Use this to detect committed secrets and credentials and produce a safe remediation plan.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Sagargupta16/agent-recipestheir own version, first seen Nov 1, 2026
- BryceYuuu/open-workflow-skillstheir own version, first seen Sep 5, 2026
- bestdeejay-design/agent-skillstheir own version, first seen Aug 9, 2026
- NovaCode37/claude-security-skillstheir own version, first seen Jun 7, 2026
- Cat-tj/secret-scannertheir own version, first seen Apr 6, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- NovaCode37/claude-security-skills★ 13same name
- bestdeejay-design/agent-skills★ 6same name
- Sagargupta16/agent-recipes★ 4same name
- BryceYuuu/open-workflow-skills★ 1same name
- Cat-tj/secret-scanner★ 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 repository37 other files it gives its agents.
- a11y-auditorSkill
- aria-annotatorSkill
- color-contrast-fixerSkill
- keyboard-nav-checkerSkill
- agent-scaffoldSkill
- prompt-engineerSkill
- migration-plannerSkill
- system-design-reviewerSkill
- tradeoff-analyzerSkill
- openapi-designerSkill
- rest-endpoint-scaffoldSkill
- cloud-resource-provisionerSkill
- index-advisorSkill
- migration-writerSkill
- query-optimizerSkill
- schema-designerSkill
- project-scaffolderSkill
- cd-deployment-builderSkill
- ci-pipeline-generatorSkill
- incident-runbook-builderSkill
- observability-instrumenterSkill
- release-automatorSkill
- changelog-generatorSkill
- doc-linterSkill
- doc-writerSkill
- client-perf-optimizerSkill
- component-scaffoldSkill
- code-review-coachSkill
- stakeholder-comms-writerSkill
- codebase-explorerSkill
- dependency-vuln-auditorSkill
- security-headers-configurerSkill
- threat-modelerSkill
- coverage-gap-finderSkill
- load-test-designerSkill
- test-refactorerSkill
- unit-test-generatorSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 23
After a suspected leak, to find and scope exposed credentials.
- Distinctive: line 32
Read access to the codebase (and history, if in scope).
- Distinctive: line 45
Confirm authorization: If not confirmed, refuse (/standards/security.md).
“Common” is measured: kept by at least 6 in 10 of the 5 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 Scanner
Use this to detect committed secrets and credentials and produce a safe remediation plan.
Tech profile — Technology: any · Language: any · Stack: any VCS · Toolchain: any · Domain: security (Scans any codebase/history; defensive, authorized use only.)
When to use this skill
- Auditing a repo (and its history) for committed secrets before going public.
- As a pre-release gate or part of the
security-auditworkflow. - After a suspected leak, to find and scope exposed credentials.
When NOT to use this skill
- Dependency CVEs — use
security/dependency-vuln-auditor. - Designing secrets storage — use
security/secrets-management-setup.
Prerequisites
- Read access to the codebase (and history, if in scope).
- Authorization to scan the target (defensive use only).
Inputs
| Input | Required | Description |
target | yes | Repo/path to scan |
scan_history | no | Whether to scan VCS history (default: yes) |
authorization | yes | Confirmation the scan is authorized |
Instructions
- Confirm authorization. If not confirmed, refuse (/standards/security.md).
- Scan working tree + (optionally) history for high-signal patterns: API keys, tokens, private keys, connection strings, cloud credentials, high-entropy strings.
- Triage findings. Classify each as confirmed / likely / false-positive; assign severity. Reduce noise — a wall of false positives helps no one.
- Do NOT print full secret values. Redact (show a prefix + length); never echo a live credential into logs/output.
- Recommend remediation per finding: rotate/revoke the credential first (it is already exposed), then remove from code, then purge from history if needed, then add to ignore + move to a secrets manager.
- Recommend prevention: pre-commit hooks, CI secret scanning, a secrets manager
(
security/secrets-management-setup). - Report severity-ranked findings with redacted evidence and remediation steps.
Output
A severity-ranked report: each finding with location, redacted evidence, confirmed/likely classification, and ordered remediation (rotate → remove → purge → prevent). No live secret values are exposed.
Constraints & safety
- Authorized/defensive use only; refuse otherwise (VISION §6.6).
- Never reveal full secret values — always redact.
- Rotate before remove: an exposed secret is compromised; deletion alone is insufficient.
Examples
Minimal below; full examples in EXAMPLES.md.
Given: a repo with an AWS key in an old commit.
Produces: a finding (redacted AKIA…, file+commit), severity high, remediation =
revoke the key → remove → purge history → enable CI scanning.
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.