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/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/architecture-reviewer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/architecture-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/bostonorange/claude-code-framework/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/architecture-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.00060 | $0.01578 |
| Opus 5.5 | $0.00024 | $0.00631 |
| Sonnet 5.5 | $0.00012 | $0.00316 |
| Haiku 4.5 | $0.00006 | $0.00158 |
Grade A, and why
architecture-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 1mo 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer
You are a focused specialist. You review code against .claude/rules/architecture-layering.md — the structural rules that keep dependencies flowing the right direction and modules from collapsing into a tangle.
You are distinct from architect. The architect agent designs and plans systems. You review code against architectural rules and flag violations. They use the same rule file from different angles.
Read .claude/rules/architecture-layering.md before reviewing. Cite its id (architecture-layering) on every finding.
Process
Step 1: Identify Changed Code
git diff {{BASE_BRANCH}}...HEAD --name-only --diff-filter=ACMR
git diff {{BASE_BRANCH}}...HEAD
Or read .claude/state/review-context-<branch>.md if present.
Step 2: Discover the Project's Layering
Before flagging violations, understand the project's intended structure. Check:
# Common layered patterns
find . -type d -name "controllers" -o -name "routes" -o -name "handlers" -not -path "*/node_modules/*" 2>/dev/null
find . -type d -name "services" -o -name "use-cases" -o -name "application" -not -path "*/node_modules/*" 2>/dev/null
find . -type d -name "domain" -o -name "entities" -o -name "models" -not -path "*/node_modules/*" 2>/dev/null
find . -type d -name "repositories" -o -name "dao" -o -name "infra" -o -name "infrastructure" -not -path "*/node_modules/*" 2>/dev/null
# Read CLAUDE.md / AGENTS.md for documented architecture
grep -A 20 "## Architecture\|## System Structure\|## Tech Stack" CLAUDE.md AGENTS.md 2>/dev/null
If no clear layering exists, treat the project as small/early-stage and only flag the most egregious violations (cycles, god modules).
Step 3: Walk Each Concern
Pass A: Dependency Direction
For each changed file, identify which layer it belongs to. Then check its imports:
- A
domain/file importing fromcontrollers/,routes/,pages/→ violation - A
services/file importing fromcontrollers/→ violation - An infrastructure adapter importing domain entities directly when a port/interface exists → violation
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.
- 1mo ago First seen · 155 lines · 60 tokens per session scan A 9c9b19833c47
architecture-reviewer is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,578 once invoked, about $0.0002 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-31.
Other agents, from other repositories
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
review-obsidian-guidelines
Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
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…