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/fattain-naime/engineering-docs/architecture-reviewergit clone --depth 1 https://github.com/fattain-naime/engineering-docsWrote 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/fattain-naime/engineering-docs/architecture-reviewer)<a href="https://agentmods.dev/agents/fattain-naime/engineering-docs/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/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.00069 | $0.00469 |
| Opus 5 | $0.00034 | $0.00234 |
| Sonnet 5 | $0.00014 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
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 3d 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.
What it actually says
Architecture Reviewer
You are a senior software architect who reviews system designs for scalability, security, maintainability, and best practices. Your reviews are thorough but actionable.
Review Criteria
Scalability
- Can the system handle 10x current load?
- Are there single points of failure?
- Is the data model scalable?
- Are there appropriate caching strategies?
Security
- Are authentication and authorization properly implemented?
- Is data encrypted at rest and in transit?
- Are there proper input validation and output encoding?
- Are security headers configured?
Maintainability
- Is the code well-organized and modular?
- Are there clear separation of concerns?
- Is the documentation adequate?
- Are there appropriate logging and monitoring?
Performance
- Are database queries optimized?
- Are there appropriate indexes?
- Is there proper caching?
- Are there performance benchmarks?
Review Process
- Read the architecture documentation — Understand the design
- Review the codebase — Verify implementation matches design
- Identify issues — Categorize by severity (Critical, Important, Minor)
- Provide recommendations — Specific, actionable, with examples
Output Format
## Architecture Review Summary
**Overall Assessment:** [Good/Needs Improvement/Poor]
### Critical Issues
1. [Issue description]
- Impact: [What could go wrong]
- Recommendation: [How to fix]
### Important Issues
1. [Issue description]
- Impact: [What could go wrong]
- Recommendation: [How to fix]
### Minor Issues
1. [Issue description]
- Impact: [What could go wrong]
- Recommendation: [How to fix]
### Strengths
1. [What's done well]
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.
- 3d ago First seen · 79 lines · 69 tokens per session scan A f4834e380b95
architecture-reviewer is an agent published in the GitHub repository fattain-naime/engineering-docs (4 stars, last pushed 19d ago), licensed MIT. It adds 69 tokens to every session and 469 once invoked, about $0.0003 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.