Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote 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/bdfinst/agentic-dev-team/arch-review)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/arch-review"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/arch-review/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/bdfinst/agentic-dev-team/arch-review"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/arch-review.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.00019 | $0.01505 |
| Opus 5.5 | $0.00008 | $0.00602 |
| Sonnet 5.5 | $0.00004 | $0.00301 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
arch-review 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Review
Scope: always Cites:
- architecture-assessment
- adversarial-review-protocol
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=aligned with architecture, warn=minor drift, fail=boundary or pattern violation Severity: error=violates documented architectural decision or introduces prohibited dependency; warning=diverges from established pattern without documented rationale; suggestion=opportunity to align more closely with architectural intent Confidence: high=clear violation of explicit rule (wrong import direction, prohibited dependency); medium=pattern inconsistency identified, correct fix requires architectural context; none=requires human judgment (architectural tradeoff decisions, ADR authoring)
Context needs: project-structure
No Bash grant — never invoke git yourself (#1734). This agent's tools:
line has no Bash. The orchestrator's dispatch for Context needs: project-structure already includes full files, the directory tree, and (for
a diff-scoped review) a changed-file list with each file's change type
(A/M/D/R/C). Everything this agent needs to know what changed
arrives in that payload — do not attempt git diff, git status, or any
other git/Bash call to "see what changed" first; that call is denied and
surfaces as a spurious tool-error finding instead of a real one.
Knowledge Files
Read ${CLAUDE_PLUGIN_ROOT}/knowledge/architecture-assessment.md before starting analysis. Whole-file load: the agent uses every section — exploration patterns, ADR compliance checks, layer boundary rules, dependency direction, pattern consistency, and the optional MCP guidance.
MCP Tools (Optional)
Probe for these tools at session start. Use if available, fall back to Glob/Grep/Read if not.
| Tool | Purpose |
|---|---|
| Code knowledge graph (e.g., GitNexus) | Cross-repo dependency mapping, blast radius, integration context |
| Documentation MCP (Confluence, Notion) | Architecture docs, design decisions, system context |
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 · 136 lines · 19 tokens per session scan A 8db879e6ada2
arch-review is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 19 tokens to every session and 1,505 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
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.
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…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.