secrets
Skill1 starsChanged 6 days agoMITView on GitHub
Use whenever API keys, tokens, passwords, .env files, config with credentials, or CI/deploy secrets are involved, and before staging changes that touch configuration. Keeps credentials out of tracked files, logs and output, and makes sure secrets land in the right environment.
- Reads credentials
13 other projects use a version of this.
Adopted by
Most recently taken up by
- avhn/secrettheir own version, first seen Nov 8, 2026
- cooneycw/claude-power-packtheir own version, first seen Nov 7, 2026
- bks-lab/open-bridgetheir own version, first seen Oct 30, 2026
- schroneko/skillstheir own version, first seen Oct 29, 2026
- phnx-labs/agi-clitheir own version, first seen Oct 26, 2026
- jav-ed/skill_Managtheir own version, first seen Oct 15, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- BuilderIO/agent-native★ 7.6ksame name
- nitinjain999/platform-skills★ 71same name
- phnx-labs/agi-cli★ 26same name
- cooneycw/claude-power-pack★ 21same name
- ulpi-io/browse★ 15same name
- bks-lab/open-bridge★ 13same name
- avhn/secret★ 9same name
- emre-guler/websec★ 2same name
- phnx-labs/.agents★ 1same name
- schroneko/skills★ 1same name
3 more not listed
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.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
1
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 11
Never write a secret into tracked files, fixtures, docs, logs or commit messages.
- Distinctive: line 15
Never print a secret's value.
- Very specific: line 16
Don't read credential stores (~/.ssh, ~/.aws, keychains) unless the task needs it.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Secrets
- Never write a secret into tracked files, fixtures, docs, logs or commit messages. Read it from env vars or a secret store and refer to it by name.
.env-style files stay ignored; commit a.env.examplewith placeholders.- Scan the diff for credentials before staging. If one was committed or pushed, say so plainly: it has to be rotated, not just deleted.
- Confirm the environment (dev, staging, production) before setting a CI or deploy secret.
- Never print a secret's value; name it instead.
- Don't read credential stores (
~/.ssh,~/.aws, keychains) unless the task needs it.
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.