Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add jl-cmd/claude-dev-env/plugin install claude-dev-envWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jl-cmd/claude-dev-env/privacy-hygiene)<a href="https://agentmods.dev/skills/jl-cmd/claude-dev-env/privacy-hygiene"><img src="https://agentmods.dev/badge/skills/jl-cmd/claude-dev-env/privacy-hygiene.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00076 | $0.01113 |
| Opus 5 | $0.00038 | $0.00557 |
| Sonnet 5 | $0.00015 | $0.00223 |
| Haiku 4.5 | $0.00008 | $0.00111 |
Grade B, and why
privacy-hygiene scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
Hooks register via `hooks/hooks.json` into `~/.claude/settings.json`. Once installed, the same gates apply in every repository the agent touches — private or public. How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
privacy-hygiene
Overview
Find and remove personal data and high-confidence secrets before they land in git history or a durable GitHub post. The pii_prevention_blocker hook blocks the common cases at write, post, and commit time. This skill is the full sweep when you need a broader pass or a remediation plan.
Announce at start: "Running privacy-hygiene sweep."
When to run a full sweep
- Before the first push of a branch that touched logs, screenshots, config samples, or machine-local paths
- After a hook block on email, home path, LAN address, or secret material
- Before opening a PR to a repository that is public (or will be made public)
- After pasting support tickets, env dumps, or terminal transcripts into the tree
What the automated gate blocks
| Category | Blocked examples | Allowed residual |
|---|---|---|
[email protected] |
[email protected], [email protected], [email protected] |
|
| Home path | C:/Users/example/..., /Users/example/..., /home/example/... |
C:/Users/example/..., C:/Users/<you>/..., /Users/alice/... |
| LAN address | Unlisted 10.x / 172.16–31.x / 192.168.x |
Public addresses; your NAS host from CLAUDE_NAS_HOST or ~/.claude/local-identity.json; entries in ALL_ALLOWLISTED_PRIVATE_IP_ADDRESSES |
| Secret | ghp_…, github_pat_…, AKIA…, PEM private-key headers |
Public keys, redacted ***, env var names without values |
Surfaces:
- Write / Edit / MultiEdit — payload text about to land on disk (via PreToolUse dispatcher)
- Durable posts —
gh pr/issue create|comment|edit|reviewbodies and GitHub MCP body/comment fields (Bash and PowerShell) - git commit — staged blob text (non-exempt paths) on Bash and PowerShell, including
git.exeand flag forms (--no-verify,-c,-C). Commit message bodies (-m/-F) are out of scope for the automated gate
Sweep procedure
Run the full-tree sweep in
reference/sweep-procedure.md: scope the tree,
run the ripgrep pass for the four high-confidence pattern families (email, home
path, LAN address, secret), review each hit against the ignore list, and
remediate. It also lists the accepted residual — what to leave in place rather
than over-scrub. The ripgrep command is the only full-tree pass; the write-time
pii_prevention_blocker scans one payload at a time.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 69 lines · 76 tokens per session scan B 6abad18290bf
privacy-hygiene is a skill published in the GitHub repository jl-cmd/claude-dev-env (5 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 1,113 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".