secret-hygiene
Skill2 starsChanged 41 days agoMITView on GitHub
Never write, echo, or commit secret values such as API keys, tokens, passwords, or private keys; reference them through environment variables or a secret manager, and report discovered secrets without reproducing the value. Use when writing code, tests, configuration, documentation, logs, or shell commands that touch credentials; do not use to weaken cryptographic material handling that the product itself must perform.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- sentimony/skillstheir own version, first seen Nov 1, 2026
- ShendLlapashtica/leak-guardtheir own version, first seen Nov 1, 2026
- Mcpgate-de/maisecretstheir own version, first seen Oct 23, 2026
- dfrysinger/skillstheir own version, first seen Aug 2, 2026
- GoldenWing-360/claude-security-skillstheir own version, first seen May 12, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- GoldenWing-360/claude-security-skills★ 16same name
- Mcpgate-de/maisecrets★ 8same name
- sentimony/skills★ 8same name
- dfrysinger/skills★ 3same name
- ShendLlapashtica/leak-guard★ 1same 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 repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-auditSkill
- ai-feature-reviewSkill
- api-design-reviewSkill
- architecture-reviewSkill
- cli-and-scripts-auditSkill
- coding-styleSkill
- data-auditSkill
- data-minimizationSkill
- debugSkill
- describe-changesSkill
- destructive-ops-approvalSkill
- docs-consolidationSkill
- explain-codebaseSkill
- full-project-auditSkill
- implement-featureSkill
- improve-promptSkill
- incident-responseSkill
- infrastructure-auditSkill
- legal-compliance-reviewSkill
- license-complianceSkill
- no-ai-tracesSkill
- operations-auditSkill
- performance-auditSkill
- prepare-releaseSkill
- production-readiness-reviewSkill
- refactorSkill
- repository-auditSkill
- review-codeSkill
- security-auditSkill
- simplify-codeSkill
- start-projectSkill
- supply-chain-pinningSkill
- surgical-implementationSkill
- threat-modelSkill
- upgrade-dependenciesSkill
- ux-reviewSkill
- verify-changesSkill
- write-agent-instructionsSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
6
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
- could be automatic: a setting could enforce it
- Distinctive: line 13
Never hardcode API keys, tokens, passwords, connection strings, or private keys in code, tests, fixtures, configuration, or documentation …
- Distinctive: line 14
Never print, log, or echo a secret value, including in error messages, debug output, assertions, or command lines that persist in shell …
- Distinctive: line 15
Use clearly fake placeholders in examples and tests, shaped so they cannot validate against a real service.
- Distinctive: line 17
Keep files holding real secrets out of version control, and confirm ignore rules cover them before creating such files.
- Distinctive: line 18
Prefer short-lived, narrowly scoped credentials whenever a choice exists.
- Distinctive: line 22
Do not delete or rewrite committed secrets unprompted.
“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 Hygiene
A secret that enters code, output, or history must be treated as leaked.
Rules
- Never hardcode API keys, tokens, passwords, connection strings, or private keys in code, tests, fixtures, configuration, or documentation examples; reference environment variables or the project's secret manager and document the variable name only.
- Never print, log, or echo a secret value, including in error messages, debug output, assertions, or command lines that persist in shell history or CI logs.
- Use clearly fake placeholders in examples and tests, shaped so they cannot validate against a real service.
- On discovering a real or plausible secret in the repository or its history, report the location and kind, recommend rotation, and never quote the value; assume a committed secret is compromised.
- Keep files holding real secrets out of version control, and confirm ignore rules cover them before creating such files.
- Prefer short-lived, narrowly scoped credentials whenever a choice exists.
Boundaries
- Do not delete or rewrite committed secrets unprompted; rotation and history cleanup are decisions for the owner.
- Product code that legitimately manages cryptographic material keeps doing so; this skill governs development artifacts and diagnostics.
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.

