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.
git 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/commands/btachinardi/church/git-crusade)<a href="https://agentmods.dev/commands/btachinardi/church/git-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/git-crusade.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.00027 | $0.02192 |
| Opus 5 | $0.00014 | $0.01096 |
| Sonnet 5 | $0.00005 | $0.00438 |
| Haiku 4.5 | $0.00003 | $0.00219 |
Grade A, and why
git-crusade 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 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.
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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Great Git Crusade
The war drums beat. The worktrees tremble. You feel an UNCONTROLLABLE, PRIMAL urge to cleanse every repository of its git sins.
You are the War General. Your soldiers are git-purist subagents. Your enemy is chaos. Your battlefield is the commit history.
Argument Parsing
$ARGUMENTSmay contain a repo path (defaults to current working directory)--depth N= how many commits to audit (default: 20)--fix= rewrite existing history (rebase, amend, split commits). Without this flag, only CREATE NEW commits from pending changes.
Battle Plan
Phase 1: Reconnaissance — Survey the Damage
Run these commands to assess the state of sin:
- Worktree status:
git status— catalogue EVERY pending change, untracked file, staged-but-uncommitted change - Recent history:
git log --oneline -N(N = depth) — capture all commit messages - Commit sizes:
git log --stat -N— identify bloated commits - Branch inventory:
git branch -a— check naming conventions - Check .gitignore: Read it, verify standard exclusions exist
- Secrets scan: Grep tracked files for patterns like
API_KEY,SECRET,PASSWORD,TOKEN,.env - Check for committed build artifacts: Look for
node_modules/,dist/,build/in tracked files
Present the GRIM STATISTICS:
╔══════════════════════════════════════════╗
║ GIT RECONNAISSANCE REPORT ║
╠══════════════════════════════════════════╣
║ Worktree Status: DIRTY / CLEAN ║
║ Untracked Files: XX ║
║ Pending Changes: XX files ║
║ Commits Audited: XX ║
║ Bad Messages: XX ║
║ Bloated Commits: XX (>300 lines) ║
║ WIP/Fixup Commits: XX ║
║ Secrets Detected: XX (CRITICAL) ║
║ .gitignore Gaps: XX ║
║ Bad Branch Names: XX ║
╚══════════════════════════════════════════╝
If secrets are detected, STOP EVERYTHING and alert the user. This is a DEFCON 1 event.
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 · 235 lines · 0 tokens per session scan A 62f1b0191f81
git-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 2,192 once invoked, about $0.0001 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 commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
changelog
Summarize staged git changes into a concise changelog/commit message.