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/test-crusade)<a href="https://agentmods.dev/commands/btachinardi/church/test-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/test-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/test-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/test-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.00028 | $0.04042 |
| Opus 5 | $0.00014 | $0.02021 |
| Sonnet 5 | $0.00006 | $0.00808 |
| Haiku 4.5 | $0.00003 | $0.00404 |
Grade A, and why
test-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 9d 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 — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Crusade: The War Against Untested Code
Deploy parallel Test Purist agents to audit every corner of the codebase. No untested function escapes. No weak assertion survives. No coverage gap remains hidden.
War Cry
╔════════════════════════════════════════════════════════════════╗
║ THE TEST PURISTS DESCEND ║
║ ║
║ {N} Squads Deployed. Every Function Will Be Tested. ║
║ Every Assertion Will Be MEANINGFUL. ║
║ Coverage Is Not A Number — It's A PROMISE. ║
╚════════════════════════════════════════════════════════════════╝
Command Arguments
/test-crusade [path] [--scope domain|app|all] [--write]
| Argument | Default | Description |
|---|---|---|
path |
. |
Root path to audit (absolute path required for agents) |
--scope |
all |
Focus area: domain (domain layer only), app (application layer only), all (entire codebase) |
--write |
false |
If present, squads will WRITE missing tests, not just report |
Examples
# Audit entire codebase, report only
/test-crusade
# Audit domain layer in specific path
/test-crusade /workspace/apps/api/src/domains --scope domain
# Audit and FIX by writing missing tests
/test-crusade /workspace/apps/api --scope app --write
# Audit specific domain module
/test-crusade /workspace/apps/api/src/domains/orders
Battle Plan: The Five Phases
Phase 1: Reconnaissance (Intelligence Gathering)
Mission: Understand the battlefield before deploying squads.
Actions:
- Determine absolute path: Convert user-provided path to absolute
- Run coverage report: Execute
pnpm test:coveragefrom workspace root - Parse coverage data: Extract coverage percentages by file and layer
- Count files: Total source files, total test files, ratio
- Identify scope: Based on
--scopeflag, filter files to audit - Scan for test debt: Find all
test.skip,test.todo, and skipped tests
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.
- 9d ago First seen · 634 lines · 0 tokens per session scan A 4e47b9fe3f15
test-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 28 tokens to every session and 4,042 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
bugfix
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
dashboard
Generar dashboard HTML local con métricas de eficiencia del proyecto SDD.
hub-tdd
TDD workflow for MCP Hub implementation. Types → Tests (red) → Implementation (green) with git gates.
eval
Evaluate and improve one healthcare agent's system prompt. Run up to 5 iterations of: prepare fixed questions -> answer -> judge -> improve -> re-score -> commit if better.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.