agentleFS
Sign inStart free
OneByJorahOneByJorah/VirtOffice/.agents/skills/security-scrub/SKILL.md

security-scrub

Skill23 starsChanged 15 days agoMITView on GitHub

Find and remove secrets, real hostnames, IPs, credentials, and private data from a repo before publishing. Use before any public release, screenshot commit, or README update.

  • Reads credentials

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Search tracked files for: private IP ranges (10., 172.16-31., 192.168.), tailnet IPs (100.64-127.), internal domains, emails, usernames, …

    line 11
  2. Distinctive:

    Check docs, screenshots, logs, and issue templates, not just code.

    line 12
  3. Very specific:

    Run trivy image on the built image and review HIGH and CRITICAL results.

    line 15
  4. Distinctive:

    Never print a secret value in output, logs, or reports.

    line 19

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

security-scrub

Checks

  1. gitleaks detect --redact --no-banner over the full history. Any finding means the secret is compromised: report it, never print it, and ask the owner to rotate it.
  2. Search tracked files for: private IP ranges (10., 172.16-31., 192.168.), tailnet IPs (100.64-127.), internal domains, emails, usernames, tokens, API keys, .env files, SSH keys.
  3. Check docs, screenshots, logs, and issue templates, not just code.
  4. Confirm .gitignore covers .env* (except .env.example) and key files.
  5. Confirm compose files bind to 127.0.0.1 and contain no credentials.
  6. Run trivy image on the built image and review HIGH and CRITICAL results.

Rules

  • Never print a secret value in output, logs, or reports. Redact.
  • Removing a secret from the latest commit does not remove it from history. Say so and ask before rewriting history. Never force-push without approval.
  • Replace real examples with clearly fake ones (example.com, 192.0.2.x, user@example.com).

Report

List findings by file and line with severity, no secret values, and the fix applied or needed.

Download now (ZIP)

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. OneByJorah/offivo★ 17100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    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 repository7 other files it gives its agents.

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.

Check your setup, free