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 commands/btachinardi/church/react-crusadegit 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/react-crusade)<a href="https://agentmods.dev/commands/btachinardi/church/react-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/react-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 | $0.00034 | $0.06019 |
| Opus 5 | $0.00017 | $0.03010 |
| Sonnet 5 | $0.00007 | $0.01204 |
| Haiku 4.5 | $0.00003 | $0.00602 |
Grade A, and why
react-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 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 — 745 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Crusade: The War Against Impure Components
Deploy parallel React Purist agents to audit every component, every hook, every effect. No tier violation escapes. No rogue effect survives. No state management sin remains hidden.
War Cry
╔════════════════════════════════════════════════════════════════╗
║ THE REACT PURISTS DESCEND ║
║ ║
║ {N} Squads Deployed. Every Component Will Be Classified. ║
║ Every Effect Will Be CLEANSED. ║
║ The Immutable State Demands PURITY. ║
╚════════════════════════════════════════════════════════════════╝
Command Arguments
/react-crusade [path] [--scope architecture|effects|state|all] [--write]
| Argument | Default | Description |
|---|---|---|
path |
. |
Root path to audit (absolute path required for agents) |
--scope |
all |
Focus area: architecture (tier compliance), effects (hook discipline), state (state management), all (complete audit) |
--write |
false |
If present, squads will REFACTOR components, not just report |
Examples
# Full frontend audit
/react-crusade
# Audit component architecture only
/react-crusade /workspace/apps/web/src --scope architecture
# Audit and FIX effect violations
/react-crusade /workspace/apps/web/src/domains --scope effects --write
# Audit specific domain's frontend
/react-crusade /workspace/apps/web/src/domains/orders
# Audit state management patterns
/react-crusade /workspace/apps/web/src --scope state
Battle Plan: The Five Phases
Phase 1: Reconnaissance (Intelligence Gathering)
Mission: Map all frontend components and classify the battlefield.
Actions:
- Determine absolute path: Convert user-provided path to absolute
- Discover component files: Glob for all
*.tsxfiles (excluding tests, stories, index files) - Count components: Total component files, hooks, stores, providers
- Scan imports: Extract import patterns to pre-classify tiers
- Identify frameworks: Detect query library (TanStack Query, SWR, etc.), state library (Zustand, Redux, etc.)
- Scan for red flags: Quick grep for
useEffect.*fetch,eslint-disable.*exhaustive-deps, excessiveuseState
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 · 745 lines · 0 tokens per session scan A 8782685594bf
react-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 6,019 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
frontend
Injects context of all relevant cli files.
component
Scaffold a new React component grounded in the paper-mono primitives. Requires explicit kind or a nearest-existing-component match. No empty divs, no speculative scaffolding.
replan-remaining-work
Command "replan-remaining-work" from udecode/plate, covering command: re-plan remaining work, when to run, hard rule, invocation and refresh afterward.
speckit-gaia-plan-close
Close a plan after implementation+merge. Offers wiki-promote for the plan's consolidated SUMMARY.md, cold-consolidates an out-of-band merge, then early-reaps the local plan folder once cost is represented in cost.jsonl.
prototype-loop
Enter leveraged-prototype focus mode — focus marker plus normal watch/rebuild loop for visual-parity work and batch upstream framework gap-fixes.
review-arch
Review the current branch for code quality, TypeScript, and React/Next.js patterns. Supports whole-branch review or scoped review by path, feature, or base branch.