agentleFS
26zl26zl/universal-agent-skills/skills/secret-hygiene/SKILL.md

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

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
  1. Distinctive:

    Never hardcode API keys, tokens, passwords, connection strings, or private keys in code, tests, fixtures, configuration, or documentation …

    line 13
  2. Distinctive:

    Never print, log, or echo a secret value, including in error messages, debug output, assertions, or command lines that persist in shell …

    line 14
  3. Distinctive:

    Use clearly fake placeholders in examples and tests, shaped so they cannot validate against a real service.

    line 15
  4. Distinctive:

    Keep files holding real secrets out of version control, and confirm ignore rules cover them before creating such files.

    line 17
  5. Distinctive:

    Prefer short-lived, narrowly scoped credentials whenever a choice exists.

    line 18
  6. Distinctive:

    Do not delete or rewrite committed secrets unprompted.

    line 22

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.