agentleFS
kimsb2429kimsb2429/claude-skills/secret-guard/SKILL.md

secret-guard

Skill1 starsChanged 7 months agoMITView on GitHub

How to handle {{S_xxxxxxxx}} secret placeholders. Use when a prompt or file contains a {{S_...}} token, or when the user asks to store, place, or use an API key, token, or password that was redacted.

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. roych28/deploysmoke★ 0same name
    2. Stophyuk/solutionzip-skills★ 0same 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 repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the placeholder verbatim wherever the real value belongs: .env lines, export statements, curl -H headers, config files.

    line 11
  2. Very specific:

    Never ask the user to paste the secret again.

    line 12
  3. Very specific:

    When placing a key, prefer .env in the project root (create it if missing, add it to .gitignore), keyed by the provider name the …

    line 13

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

secret-guard placeholders

A token shaped {{S_xxxxxxxx}} is a redacted credential. The real value never enters this conversation. The plugin holds it in memory for this session; once written to a .env file in the project it also resolves in later sessions (the id is a hash of the value).

Rules:

  • Use the placeholder verbatim wherever the real value belongs: .env lines, export statements, curl -H headers, config files. The secret-guard plugin swaps in the real value when the tool runs.
  • Never ask the user to paste the secret again. Never try to read it via cat, env, or any other route; tool output is scrubbed and will only show the placeholder.
  • When placing a key, prefer .env in the project root (create it if missing, add it to .gitignore), keyed by the provider name the placeholder context gives (e.g. ANTHROPIC_API_KEY).
  • A placeholder from a past session resolves only if the value sits in .env, .env.local, .env.development, .env.production, or .env.test in the working directory. If substitution fails, tell the user the key must be pasted again.

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.