Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/rohirik/claude-code-config/precommitsanitizenpx skills add RohiRIK/claude-code-config --skill precommitsanitizegit clone --depth 1 https://github.com/RohiRIK/claude-code-configWrote 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/rohirik/claude-code-config/precommitsanitize)<a href="https://agentmods.dev/skills/rohirik/claude-code-config/precommitsanitize"><img src="https://agentmods.dev/badge/skills/rohirik/claude-code-config/precommitsanitize.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.00058 | $0.01240 |
| Opus 5 | $0.00029 | $0.00620 |
| Sonnet 5 | $0.00012 | $0.00248 |
| Haiku 4.5 | $0.00006 | $0.00124 |
Grade A, and why
PreCommitSanitize scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Commit Sanitization
When This Applies
Before every git add or git commit in ~/.claude, scan staged files for sensitive personal information that should not be pushed to a public GitHub repository.
What to Catch
Hardcoded Home Paths
Any absolute path containing a username or home directory:
| Pattern | Example | Fix |
|---|---|---|
/Users/<username>/ |
/Users/jane/.claude/hooks/... |
~/.claude/hooks/... |
/home/<username>/ |
/home/deploy/.claude/... |
~/.claude/... |
C:\Users\<username>\ |
C:\Users\jane\... |
~\.claude\... |
Exception: .gitignore rules may use relative paths that are fine.
Personal Identifiers
| Pattern | Example | Action |
|---|---|---|
| Email addresses | [email protected] |
Remove or replace with [email protected] |
| Social media handles | linkedin.com/in/<handle> |
Remove unless intentionally public (README author section) |
| Machine hostnames | <Name>-MacBook-Pro.local |
Remove |
| Usernames in paths | username embedded in file content | Replace with ~ or $HOME |
Exception: README.md author/contact section may intentionally include social links — confirm before removing.
Symlinks
Rule: No symlink inside ~/.claude/ may be committed to git.
Symlinks are always machine-specific — they point to absolute paths on the local filesystem that don't exist on other machines. Committing them breaks clones and leaks personal paths.
| Action | When |
|---|---|
Add to .gitignore under # Symlinks section |
When creating any new symlink inside ~/.claude/ |
Run git rm --cached <path> |
If a symlink was accidentally tracked |
The hooks/git/pre-commit hook auto-detects and blocks staged symlinks (git mode 120000) and adds them to .gitignore automatically. This is a safety net — always add manually first.
Pattern for .gitignore:
# Symlinks (local-only, machine-specific — never commit symlinks to shared tools)
# Rule: ANY symlink inside ~/.claude/ must be listed here.
skills/MySkilLink
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.
- 5d ago First seen · 110 lines · 58 tokens per session scan A a542ce5b8a5a
PreCommitSanitize is a skill published in the GitHub repository RohiRIK/claude-code-config (10 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,240 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
commit
Commit current changes with a clear, descriptive message.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…