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/arch-crusade)<a href="https://agentmods.dev/commands/btachinardi/church/arch-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/arch-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/arch-crusade"><img src="https://agentmods.dev/badge/commands/btachinardi/church/arch-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.00030 | $0.04449 |
| Opus 5 | $0.00015 | $0.02225 |
| Sonnet 5 | $0.00006 | $0.00890 |
| Haiku 4.5 | $0.00003 | $0.00445 |
Grade A, and why
arch-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 11d 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 — 589 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Crusade
WAR CRY: "The Architecture Purists inspect every import, every boundary, every layer. Multiple squads deployed across all domain modules. The fortress will hold — or we will REBUILD it."
Command Overview
This slash command orchestrates a comprehensive architectural audit of the entire codebase using parallel Architecture Purist agents. It detects layer violations, circular dependencies, cross-domain coupling, and structural rot across all domains.
NEW CAPABILITY: The crusade can also generate comprehensive architecture documentation including domain catalogs, context maps, target state visions, and migration plans.
Usage
/arch-crusade [path] [--domain <name>] [--fix]
Arguments:
[path]— Optional. Root path to audit (defaults to current working directory)--domain <name>— Optional. Audit specific domain only (e.g., "orders", "users")--fix— Optional. Automatically apply fixes for auto-fixable violations
Examples:
/arch-crusade # Full audit
/arch-crusade apps/api/src/domains # Backend only
/arch-crusade --domain orders # Specific domain
/arch-crusade apps/api/src/domains/orders --fix # Auto-fix violations
/arch-crusade --docs # Generate architecture docs
/arch-crusade --target-state # Design target architecture
Extended Modes:
--docs— Generate comprehensive architecture documentation (domains.md, context-map.md, etc.)--target-state— Design target state architecture with ADRs and migration plans--reconcile— Ensure all features are accounted for in architecture redesign--scenarios— Validate architecture against real-world development scenarios
Mission Phases
Phase 1: Reconnaissance
Objective: Map the battlefield. Identify all domain modules, build the dependency graph, classify layers.
Actions:
- Use
Globto find all domain modules:- Backend:
apps/api/src/domains/*/ - Frontend:
apps/web/src/domains/*/
- Backend:
- Use
Globto find all TypeScript files:**/*.ts,**/*.tsx - Use
Grepto extract all import statements across the codebase - Classify each file by layer based on directory structure:
- Files in
*/domain/→ Domain layer - Files in
*/application/→ Application layer - Files in
*/infrastructure/→ Infrastructure layer - Files in
*/presentation/→ Presentation layer
- Files in
- Build import dependency graph (adjacency list)
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.
- 11d ago First seen · 589 lines · 0 tokens per session scan A d45709f445d6
arch-crusade is a command published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 4,449 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.