secrets-management-audit
Skill47 starsChanged 5 months agoMITView on GitHub
Use when hunting for exposed secrets and auditing how an app you own manages them — API keys, tokens, passwords, and private keys in source, git history, binaries, logs, config, and CI; plus vaulting, rotation, and least-privilege of the secrets themselves.
- Reads credentials
2 other projects use a version of this.
Adopted by
Most recently taken up by
- MohOneX/claude-opus-skillstheir own version, first seen Jun 6, 2026
- JeremyMorgan/code-review-skillstheir own version, first seen Jun 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- JeremyMorgan/code-review-skills★ 15same name
- MohOneX/claude-opus-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 repository15 other files it gives its agents.
- access-control-testingSkill
- active-pentestSkill
- api-security-testingSkill
- authentication-testingSkill
- business-logic-testingSkill
- client-side-exploitationSkill
- file-upload-and-ssrfSkill
- injection-testingSkill
- pentest-reportingSkill
- recon-and-osintSkill
- security-code-auditSkill
- security-hardeningSkill
- security-testingSkill
- threat-modelingSkill
- vulnerability-chainingSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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
- could be automatic: a setting could enforce it
- Distinctive: line 64
No prevention — without pre-commit/CI scanning, the next secret lands next week.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Secrets Management Audit (FIND/FIX — credentials & keys)
Overview
Leaked secrets are among the fastest paths to compromise — one committed key can hand over a whole cloud account. This skill finds exposed secrets everywhere they hide and audits whether the app manages them properly (vaulted, rotated, scoped).
Core principle: A secret in source/history/logs/binary is already public — assume compromised and rotate. Detection without rotation is theater.
Applies when / Skip when
- Applies when: essentially always — every app has secrets/keys/config somewhere (source, git history, logs, env, build artifacts, CI).
- Skip when: effectively never. Even a static site has API keys, deploy creds, or CI tokens.
- If genuinely nothing to scan: say so explicitly — but verify first; "no secrets" is almost always "didn't look hard enough."
⚠️ Authorization
Your own/authorized repos, artifacts, and infrastructure. If you find a real exposed secret, treat it as an incident: rotate first, then fix the leak path.
Where secrets hide (hunt all of these)
| Location | How |
| Source code | Scanners + grep for key patterns |
| Git history | Secrets deleted from HEAD still live in history — scan all commits |
| Frontend bundles | JS/source maps shipping keys to the browser |
| Mobile binaries | Decompiled APK/IPA (apktool/jadx, strings) |
| Logs & error output | Tokens/PII printed to stdout/log files/APM |
| Config & env | .env, config files, container env, cloud user-data |
| CI/CD | Pipeline files, build logs, masked-but-leaked env vars |
| Cloud | Instance metadata, function env, IaC state, config |
See references/secret-hunting.md for tooling and patterns.
Method
- Scan broadly — full git history + working tree + artifacts + logs with entropy + pattern detectors.
- Validate — is the hit a live credential? (don't use third-party creds; verify benignly/own-keys only)
- Assess blast radius — what does the secret unlock? scope/permissions?
- Manage audit — are secrets vaulted, rotated, least-privilege, not in code?
- Remediate — rotate exposed secrets, purge from history, move to a manager, add prevention.
Tooling
trufflehog, gitleaks, detect-secrets (detection incl. history & entropy); git filter-repo/
BFG (purge history); cloud secret managers / Vault (storage); pre-commit hooks + CI scanning (prevent).
Output
Per finding: secret type, location (incl. commit hash), validity, blast radius, and rotation status. Live high-privilege keys are Critical — rotate immediately.
Hand-off
Chains (leaked key → account/cloud takeover) → vulnerability-chaining; fix & prevention →
security-hardening (rotate, vault, scope, pre-commit/CI secret scanning).
Common mistakes
- Scanning only HEAD — git history is where deleted secrets live forever.
- Removing a secret from code but not rotating it — it's already compromised.
- Shipping "public" keys that are actually secret/service keys in frontend/mobile bundles.
- No prevention — without pre-commit/CI scanning, the next secret lands next week.
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.