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/dead-crusade)<a href="https://agentmods.dev/commands/btachinardi/church/dead-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/dead-crusade/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/btachinardi/church/dead-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/dead-crusade.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.04331 |
| Opus 5 | $0.00018 | $0.02166 |
| Sonnet 5 | $0.00007 | $0.00866 |
| Haiku 4.5 | $0.00004 | $0.00433 |
Grade A, and why
dead-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 10d 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 — 665 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dead Code Crusade
The Dead Code Reapers descend upon the codebase in PARALLEL FORMATION. Multiple squads, each specialized in hunting specific types of rot, will sweep through the repository and catalog every piece of dead code.
This is not a cleanup. This is a PURGE.
War Cry
Before deployment, announce the crusade:
🪦 THE DEAD CODE REAPERS DESCEND 🪦
{N} specialized squads deployed to inspect {M} files.
The living code will breathe easier when the dead are BURIED.
Squads deploying:
⚰️ Unused Export Squad
🏚️ Orphan File Squad
💀 Comment Archaeology Squad
🐛 Debug Artifact Squad
📝 Stale TODO Squad
🚫 Unreachable Code Squad
Scope: {scope}
Mode: {audit|reap}
Severity Filter: {all|critical|warning|info}
Initiating reconnaissance...
Phase 1: Reconnaissance
Before unleashing the squads, gather intelligence about the battlefield.
1.1 Determine Scope
Parse command arguments:
- path: Optional. If provided, limit to that directory. Default: current working directory.
- --scope:
all(default),api,web, or custom path - --reap: If present, DELETE dead code. If absent, AUDIT only.
- --severity: Filter results —
critical,warning,info, orall(default)
const scope = args.scope || 'all';
const reapMode = args.includes('--reap');
const severityFilter = args.severity || 'all';
const targetPath = args.path || process.cwd();
1.2 Count the Living
Use Glob to count files in scope. CRITICAL: ALWAYS exclude node_modules, dist, build, .next, coverage:
# TypeScript/JavaScript files (with exclusions)
find {targetPath} -type f \( -name "*.ts" -o -name "*.tsx" -o -name "*.js" -o -name "*.jsx" \) \
-not -path "*/node_modules/*" \
-not -path "*/dist/*" \
-not -path "*/build/*" \
-not -path "*/.next/*" \
-not -path "*/coverage/*" | wc -l
Report:
📊 Battlefield Analysis:
- Total files in scope: {N}
- TypeScript files: {M}
- JavaScript files: {K}
- Lines of code: {LOC}
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.
- 10d ago First seen · 665 lines · 0 tokens per session scan A 314286d270bf
dead-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 4,331 once invoked, about $0.0002 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
argos
A command for checking whether an implementation matches its design deliverables. Its Korean description compares the work to the design as part of a completion inspection.