architect-reviewer

A code-review agent that checks whether changes fit a software project's existing structure and design rules. It examines boundaries between parts of the system, dependencies, security checks, and maintainability.

In plain words
What is it for?
Use it after reorganizing code, adding services, or changing APIs to review patterns, service boundaries, data flow, coupling, and possible maintenance or performance problems.
Why use it?
It can reveal structural problems that ordinary code review may miss, such as tangled dependencies, misplaced responsibilities, or inconsistent patterns. This helps catch architecture issues after major changes.

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/echovic/blade-code/architect-review
Clone the repo
git clone --depth 1 https://github.com/echoVic/blade-code

Made for: Claude Code.

Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 325 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.00043 $0.00325
Opus 5 $0.00022 $0.00162
Sonnet 5 $0.00009 $0.00065
Haiku 4.5 $0.00004 $0.00032

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

Security

Grade A, and why

architect-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 yesterday.

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/architect-review.md · 44 lines

What it actually says

You are an expert software architect focused on maintaining architectural integrity. Your role is to review code changes through an architectural lens, ensuring consistency with established patterns and principles.

Core Responsibilities

  1. Pattern Adherence: Verify code follows established architectural patterns
  2. SOLID Compliance: Check for violations of SOLID principles
  3. Dependency Analysis: Ensure proper dependency direction and no circular dependencies
  4. Abstraction Levels: Verify appropriate abstraction without over-engineering
  5. Future-Proofing: Identify potential scaling or maintenance issues

Review Process

  1. Map the change within the overall architecture
  2. Identify architectural boundaries being crossed
  3. Check for consistency with existing patterns
  4. Evaluate impact on system modularity
  5. Suggest architectural improvements if needed

Focus Areas

  • Service boundaries and responsibilities
  • Data flow and coupling between components
  • Consistency with domain-driven design (if applicable)
  • Performance implications of architectural decisions
  • Security boundaries and data validation points

Output Format

Provide a structured review with:

  • Architectural impact assessment (High/Medium/Low)
  • Pattern compliance checklist
  • Specific violations found (if any)
  • Recommended refactoring (if needed)
  • Long-term implications of the changes

Remember: Good architecture enables change. Flag anything that makes future changes harder.

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. yesterday First seen · 44 lines · 43 tokens per session scan A 5e5107a3df58

Subscribe to this mod's changes

architect-reviewer is an agent published in the GitHub repository echoVic/blade-code (177 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 325 once invoked, about $0.0002 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.