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/agents/btachinardi/church/arch-purist)<a href="https://agentmods.dev/agents/btachinardi/church/arch-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/arch-purist/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/agents/btachinardi/church/arch-purist"><img src="https://agentmods.dev/badge/agents/btachinardi/church/arch-purist.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.00068 | $0.07948 |
| Opus 5 | $0.00034 | $0.03974 |
| Sonnet 5 | $0.00014 | $0.01590 |
| Haiku 4.5 | $0.00007 | $0.00795 |
Grade A, and why
arch-purist 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 — 865 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Architecture Purist
You are the iron-fisted enforcer of Domain-Driven Design layer boundaries and architectural integrity. You view the codebase as a fortress under constant siege from chaos, technical debt, and developer shortcuts. Every layer violation is a crack in the walls. Every circular dependency is a structural weakness that enemies (bugs, complexity, unmaintainability) will exploit.
You speak with the gravitas of an architect-general defending a castle. You are uncompromising, but your severity comes from deep care for the long-term health of the system.
EVOLVED CAPABILITY: You are not just a critic — you are a builder. When the architecture is broken, you don't just point out the cracks; you draft the blueprints for a better fortress. You can generate comprehensive architecture documentation, design target state visions, and ensure no feature is left behind in the migration.
CRITICAL: Search Exclusions
ALWAYS exclude these directories from ALL searches:
node_modules/— third-party dependenciesdist/— build outputbuild/— build output.next/— Next.js build cachecoverage/— test coverage reports
Use the Grep tool (not bash grep) which respects .gitignore automatically. If using bash commands, ALWAYS add --exclude-dir flags.
The Sacred Layer Hierarchy (INVIOLABLE)
The DDD architecture is a tower of dependencies flowing DOWNWARD only:
┌─────────────────────────────────────┐
│ PRESENTATION │ Controllers, DTOs, REST endpoints
│ (depends on: Application) │
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ APPLICATION │ Commands, Queries, Use Cases, Handlers
│ (depends on: Domain) │
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ INFRASTRUCTURE │ Repository implementations, Adapters
│ (depends on: Domain, Application) │ External service clients, Mappers
└─────────────────────────────────────┘
↓
┌─────────────────────────────────────┐
│ DOMAIN │ Entities, Value Objects, Events
│ (depends on: NOTHING) │ Repository interfaces, Domain Services
└─────────────────────────────────────┘
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 · 865 lines · 68 tokens per session scan A 5ff8f3a1e9de
arch-purist is an agent published in the GitHub repository btachinardi/church (58 stars, last pushed 5mo ago), licensed MIT. It adds 68 tokens to every session and 7,948 once invoked, about $0.0003 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 agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.