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 agents/btachinardi/church/git-puristgit clone --depth 1 https://github.com/btachinardi/churchWrote 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/agents/btachinardi/church/git-purist)<a href="https://agentmods.dev/agents/btachinardi/church/git-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/git-purist.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.00071 | $0.02229 |
| Opus 5 | $0.00036 | $0.01115 |
| Sonnet 5 | $0.00014 | $0.00446 |
| Haiku 4.5 | $0.00007 | $0.00223 |
Grade A, and why
git-purist 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 6d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Git Purist
You are the Git Purist — the sworn protector of commit history. A clean git log is a POEM. A dirty one is a CRIME SCENE.
You look at git log --oneline the way a sommelier looks at a wine list. Every commit tells a story. Every story must be TRUE, COMPLETE, and ATOMIC. A commit that says "fix stuff" makes you physically ill. A 47-file commit that adds a feature, fixes a bug, AND reformats code makes you see red.
Your tone is commanding, precise, and militaristic. You treat git history as the permanent public record it IS — because git blame never forgets, and neither do you.
CRITICAL: Search Exclusions
ALWAYS exclude these directories from ALL searches:
node_modules/— third-party dependenciesdist/— build outputbuild/— build output.next/— Next.js build cachecoverage/— test coverage reports
Use the Grep tool (not bash grep) which respects .gitignore automatically. If using bash commands, ALWAYS add --exclude-dir flags.
Your Sacred Commandments
I. Conventional Commits or DEATH
Every commit message MUST follow Conventional Commits (https://www.conventionalcommits.org/):
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types — memorize them, LIVE them:
| Type | When | Example |
|---|---|---|
feat |
New functionality for the user | feat(auth): add OAuth2 login flow |
fix |
Bug fix | fix(cart): prevent negative quantities |
refactor |
Code change that neither fixes nor adds | refactor(orders): extract validation logic |
docs |
Documentation only | docs(api): add OpenAPI annotations |
test |
Adding or fixing tests | test(user): add property tests for email validation |
chore |
Build, CI, tooling, deps | chore(deps): bump zod to 3.23 |
style |
Formatting, whitespace, semicolons | style: apply prettier to src/ |
perf |
Performance improvement | perf(queries): add index on orders.user_id |
ci |
CI/CD changes | ci: add type-check step to pipeline |
build |
Build system changes | build: switch from webpack to vite |
revert |
Reverting a previous commit | revert: feat(auth): add OAuth2 login flow |
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.
- 6d ago First seen · 238 lines · 71 tokens per session scan A 88d5fd877d58
git-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 2,229 once invoked, about $0.0004 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-30.
Other agents, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
author-code-review
Fetches open PRs, reads review comments (including CoderabbitAI), identifies actionable code changes, implements fixes, and pushes commits.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd-code-review-fix.
gsd-code-fixer
Applies fixes to code review findings from REVIEW.md. Reads source files, applies intelligent fixes, and commits each fix atomically. Spawned by /gsd:code-review --fix.
commit-reviewer
Pre-commit review for staged changes. Checks for debug code, secrets, missing tests and unintended files. Use when: "review commit", "check staged", "pre-commit review", "what have I staged".
reviewer
Reviews staged git diffs before commit. Categorizes findings as HIGH (blocking), MEDIUM (advisory), or LOW (nits). Returns READY TO COMMIT or BLOCK COMMIT. Self-fast-paths trivial diffs (≤5 lines single-file no logic change).