agentleFS
Sign inStart free
fhgomesfhgomes/my-awesome-agents-skills/skills/redact/SKILL.md

redact

Skill5 starsChanged 40 days agoGPL-3.0View on GitHub

Privacy and data-exposure specialist for code — a PRE-PUBLICATION audit of repositories that are about to go public (or already are). Hunts leaked secrets and sensitive data: API keys, tokens, passwords, connection strings, private keys, certificates, database credentials, CI secrets, service accounts, internal IPs and hostnames, private endpoints, and personal data — PII (Brazilian CPF/RG/CNPJ IDs, e-mail, phone, address, customer names), PCI (credit card numbers, CVV), PHI (health data) — in the working tree AND in GIT HISTORY, where a leak survives even after the file is deleted. Teaches remediation: move to an environment variable, .env, application.properties, parameter, or secret manager; create .env.example; fix .gitignore; rewrite history; and rotate the exposed credential. ALWAYS use when the user says: "I'm making this repo public", "can I publish this?", "is there a secret in the code?", "did a password leak?", "check whether a key was committed", "audit before publishing", "is this repo safe to open up?", "open-source this project", "review before pushing", "is there personal data in the code?", "is there a CPF/card number in the repo?", "I committed .env by mistake", "how do I remove it from history", "how do I use an environment variable". Also trigger on mentions of: "secret", "secrets", "API key", "leaked token", "hardcoded password", "password in the code", "exposed credential", "private key", "id_rsa", ".env committed", "connection string", "PII", "PCI", "PHI", "LGPD", "GDPR", "personal data", "anonymize", "sanitize repo", "gitleaks", "trufflehog", "git history", "rewrite history", "BFG", "filter-repo", "public repository", "make public", "publish on GitHub", "open source". Also triggers on the equivalent phrases in other languages. For malware/viruses/suspicious files, use the warden skill. For server and infrastructure hardening, use the sentinel skill.

  • Reads credentials

4 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

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 4 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.

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