audit-secret-exposure
Skill7 starsChanged 49 days agoNo licenceView on GitHub
Scan an agent's context surfaces — instruction files, skill files, harness config, tool defs, and credential-bearing files — for credentials that landed where the model can read them — hardcoded keys, secrets pasted into prompts/tool args, agent-readable .env/key files with no mechanical block, long-lived keys on harness/context surfaces where short-lived tokens exist, URL query-string leak channels, secrets baked into skill examples, and control logic stored in a system prompt. Invoke when granting or hardening an agent's repo/harness and you need a deterministic literal-secret content scan. Skip when auditing a workflow file's own secrets/OIDC posture (use audit-github-actions-security), whether private-data + untrusted-input + egress co-occur on one execution path (use audit-lethal-trifecta) or auditing dependency/install sinks (use audit-supply-chain-sinks).
- Reads credentials
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- architecture-committeeSkill
- audit-geo-contentSkill
- audit-github-actions-securitySkill
- audit-harness-safetySkill
- audit-instruction-fileSkill
- audit-lethal-trifectaSkill
- audit-mcp-serverSkill
- audit-memory-retrieval-integritySkill
- audit-multi-agent-orchestrationSkill
- audit-observability-setupSkill
- audit-prompt-cache-hygieneSkill
- audit-prompt-hook-placementSkill
- audit-self-improvement-protocolSkill
- audit-skill-qualitySkill
- audit-supply-chain-sinksSkill
- audit-tool-definitionSkill
- audit-verification-gatesSkill
- compress-promptSkill
- conflicting-instruction-detectorSkill
- review-codeSkill
- write-skillSkill
- write-testsSkill
- write-tool-descriptionSkill
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.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.