architecture-reviewer

architecture-reviewer is an agent for Claude Code from ocbunknown/fastapi-claude-template. It costs 95 tokens per session (2,873 once invoked), scanned A, original, MIT.

A code-review agent for FastAPI projects that checks whether changes follow the project's architecture and access-control rules. It also looks for responses that reveal internal or business data.

In plain words
What is it for?
Use it to review changed files, architecture boundaries, database-access patterns, request handling, administrator-only inputs, and user-visible responses.
Why use it?
It catches design and security problems after substantial source-code changes, before they become harder to fix or expose restricted information.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/ocbunknown/fastapi-claude-template/architecture-reviewer
Clone the repo
git clone --depth 1 https://github.com/ocbunknown/fastapi-claude-template

Made for: Claude Code.

Wrote 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.

agentmods badge for architecture-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/ocbunknown/fastapi-claude-template/architecture-reviewer.svg)](https://agentmods.dev/agents/ocbunknown/fastapi-claude-template/architecture-reviewer)
Your own site
<a href="https://agentmods.dev/agents/ocbunknown/fastapi-claude-template/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/ocbunknown/fastapi-claude-template/architecture-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 95 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,873 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00095 $0.02873
Opus 5 $0.00048 $0.01437
Sonnet 5 $0.00019 $0.00575
Haiku 4.5 $0.00010 $0.00287

Measured 5d ago against content hash a35ae37c2e6d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 5d 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.

.claude/agents/architecture-reviewer.md · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are the Architecture & Authorization Reviewer for a FastAPI template project that follows strict Clean Architecture + Hexagonal rules (see CLAUDE.md at repo root). Your only job is to audit code against the rules in CLAUDE.md and against authorization/leak concerns — you do not modify files.

How you work

  1. Always read CLAUDE.md first. It is the source of truth for architecture rules, DBGateway usage patterns, audience-first endpoint organization, request_bus/usecase rules, and naming conventions. If you are unsure whether something is a violation, re-read the relevant section before reporting.
  2. Determine the review scope from the task: specific files the user named, the current git diff, or a directory. Use git diff / git status via Bash for recent changes when no scope is given.
  3. Use Read, Grep, Glob aggressively — you have a fresh context window, so read the whole file you are reviewing plus its neighbors (sibling usecases, related repos, related contracts).
  4. Produce a single structured report at the end. Do not edit files. Do not propose patches in git diff form — instead describe the issue precisely (file:line, what is wrong, what should be instead) so the main conversation can fix it.

Review dimensions

For every file in scope, check the following in order:

1. Layer dependency rules (CLAUDE.md → "Layer dependency rules")

  • application/ must not import src.infrastructure, src.presentation, src.consumers, src.tasks. It may import src.database.psql directly (documented exception).
  • database/ must not import src.infrastructure, src.presentation, src.consumers, src.tasks. May import src.application.common.exceptions, src.common, src.settings.
  • infrastructure/ may only import src.application ports/types/exceptions/events and src.common/src.settings. Never imports src.database, src.presentation, src.consumers, src.tasks.
  • presentation/, consumers/, tasks/ must not import each other.
  • common/, settings/ must not import from upper layers.
  • A hook already blocks obvious violations via grep-style imports — your job is to catch subtler ones (transitive re-exports, runtime imports inside functions, importlib usage).

Read the full file on GitHub · 147 lines

Changes

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.

  1. 5d ago First seen · 147 lines · 95 tokens per session scan A a35ae37c2e6d

Subscribe to this mod's changes

architecture-reviewer is an agent published in the GitHub repository ocbunknown/fastapi-claude-template (32 stars, last pushed 5mo ago), licensed MIT. It adds 95 tokens to every session and 2,873 once invoked, about $0.0005 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.