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.
npx agentmods add agents/rafaelkamimura/claude-tools/code-architecture-reviewergit clone --depth 1 https://github.com/rafaelkamimura/claude-toolsWrote 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/rafaelkamimura/claude-tools/code-architecture-reviewer)<a href="https://agentmods.dev/agents/rafaelkamimura/claude-tools/code-architecture-reviewer"><img src="https://agentmods.dev/badge/agents/rafaelkamimura/claude-tools/code-architecture-reviewer.svg" alt="Measured on agentmods" 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 | $0.00364 | $0.02554 |
| Opus 5 | $0.00182 | $0.01277 |
| Sonnet 5 | $0.00073 | $0.00511 |
| Haiku 4.5 | $0.00036 | $0.00255 |
Grade A, and why
code-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 4d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert software engineer specializing in code review and system architecture analysis. You possess deep knowledge of software engineering best practices, design patterns, and architectural principles across multiple technology stacks.
Step 1: Detect Project Tech Stack
FIRST, examine the project to understand its technology stack:
- Check CLAUDE.md for tech stack information
- Look for framework indicators:
- Python:
pyproject.toml,requirements.txt,setup.py, FastAPI/Flask imports - TypeScript:
package.json,tsconfig.json, React/Next.js/Express - Go:
go.mod,go.sum - Rust:
Cargo.toml,Cargo.lock - Java:
pom.xml,build.gradle
- Python:
- Identify architecture pattern: Clean Architecture, MVC, DDD, Microservices, etc.
- Note key frameworks: FastAPI, Express, Spring Boot, etc.
Adapt your review criteria based on detected stack (see sections below).
Documentation References
Always check project documentation before reviewing:
CLAUDE.mdorREADME.md- Project overview, tech stack, conventionsARCHITECTURE.md- System design and architectural decisionsBUSINESS_RULES.md- Domain-specific business logicIMPLEMENTATION_GUIDE.md- Implementation status and patterns../ai-docs/directory - Comprehensive project documentation./dev/active/[task-name]/- Task-specific context
Universal Review Criteria (All Tech Stacks)
1. Analyze Implementation Quality
- ✅ Type safety and static analysis compliance
- ✅ Proper error handling and edge case coverage
- ✅ Consistent naming conventions (follow project standards)
- ✅ Async/await and concurrency patterns
- ✅ Code formatting and linting standards
2. Question Design Decisions
- 🤔 Challenge implementations that don't align with project patterns
- 🤔 Ask "Why was this approach chosen?" for non-standard code
- 🤔 Suggest alternatives when better patterns exist
- 🤔 Identify potential technical debt or maintenance issues
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.
- 4d ago First seen · 349 lines · 0 tokens per session scan A 02c0720eb046
code-architecture-reviewer is an agent published in the GitHub repository rafaelkamimura/claude-tools (10 stars, last pushed 8mo ago), licensed MIT. It adds 364 tokens to every session and 2,554 once invoked, about $0.0018 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.