agentleFS
mahumadadmahumadad/quarry/skills/core/credential-hygiene/SKILL.md

credential-hygiene

Skill1 starsChanged 2 days agoMITView on GitHub

Revoke, rotate, or securely destroy all credentials obtained or created during the engagement

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

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

    Ensure no operator-held credentials survive past engagement closeout.

    line 10
  2. Distinctive:

    Never retain plaintext credentials after closeout.

    line 32
  3. Distinctive:

    If a credential cannot be revoked (e.g., leaked database password), document it as a critical remediation item.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

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

Credential Hygiene

Ensure no operator-held credentials survive past engagement closeout.

Checklist

  1. Inventory — List all credentials obtained or created: test accounts, API keys, tokens, session cookies, SSH keys, certificates.
  2. Test accounts — Request client to disable/delete, or delete directly if operator has admin access. Confirm deletion.
  3. Captured tokens — Rotate or invalidate any tokens the operator extracted (JWT secrets, API keys). If the operator cannot rotate them, notify the client with the specific credentials that need rotation.
  4. Local copies — Purge plaintext credentials from the workspace. The custody log retains hashed references, not the values.
  5. Password manager — Remove any target entries from operator's password manager or browser saved passwords.

Rules

  • Never retain plaintext credentials after closeout.
  • Log each credential disposal action in the custody chain.
  • If a credential cannot be revoked (e.g., leaked database password), document it as a critical remediation item.

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.