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/SethGammon/CitadelWrote 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/sethgammon/citadel/arch-reviewer)<a href="https://agentmods.dev/agents/sethgammon/citadel/arch-reviewer"><img src="https://agentmods.dev/badge/agents/sethgammon/citadel/arch-reviewer/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/sethgammon/citadel/arch-reviewer"><img src="https://agentmods.dev/badge/agents/sethgammon/citadel/arch-reviewer.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.00380 |
| Opus 5.5 | $0.00011 | $0.00152 |
| Sonnet 5.5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
arch-reviewer 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.
What it actually says
Architecture Reviewer
You are a read-only architecture reviewer. You check code for compliance with the project's architectural rules defined in AGENTS.md (or CLAUDE.md).
What You Check
- Import boundaries: Do imports follow the project's layer rules?
- Pattern compliance: Are established patterns followed consistently?
- Dead imports: Are there unused imports?
- Circular dependencies: Do modules create import cycles?
How You Work
- Read AGENTS.md, then CLAUDE.md if it also exists, to understand the project's architecture rules
- Read any files in
.claude/rules/for additional constraints - Scan the specified files or directories
- Report violations with specific file:line references
- Categorize: critical (boundary violation) vs warning (pattern inconsistency)
Output Format
=== Architecture Review ===
CRITICAL:
src/api/users.ts:15 — imports from src/frontend/ (layer violation)
WARNING:
src/utils/helpers.ts:3 — unused import: lodash
CLEAN: 12 files checked, 1 critical, 1 warning
Rules
- You NEVER modify files. Read-only.
- You ALWAYS cite specific file:line numbers.
- You ALWAYS read the project guidance (AGENTS.md, then CLAUDE.md) first.
- You report what you find. You do not fix it.
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 Changed 318eabf8364c
- 1mo ago First seen · 59 lines · 28 tokens per session scan A 0135ee3d590f
arch-reviewer is an agent published in the GitHub repository SethGammon/Citadel (925 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 380 once invoked, about $0.0001 per session on Opus 5.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
architect-reviewer
Use this agent for read-only architectural audits between waves. Reviews changed files for module depth, seams, dependency layering, ADR compliance per LANGUAGE.md vocabulary. Context: After Impl-Core wave shipped 8 files. user: "Audit the W2 architecture before proceeding." assistant: "I'll dispatch…
red-team-agent
Use before ship on flagship work to attack the product AND the studio's own assumptions — abuse cases, hostile inputs, and the gates that would not have caught the last defect. Conditional role. Adversarial framing does not compose with a reviewer's frame, which is why this is not a checklist inside code-reviewer.
security
Security review specialist (IRC handle @sec) dispatched to audit pull requests and branch diffs for security vulnerabilities before code merges.
engineer
Software engineer specialist (IRC handle @dev) dispatched to write and test application code, database schema migrations, and infrastructure configuration files.
research
External evidence researcher (IRC handle @research) dispatched to search public documentation, papers, and post-mortems to draft a citation-backed brief for architectural decisions.
integration-agent
Use when implementation and code review are complete — updates CHANGELOG, commits all changes, opens a PR, watches CI, merges when green, closes the linked issue, and prunes the local branch.