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.
git clone --depth 1 https://github.com/nolabs-ai/claude-extensionsWrote 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/nolabs-ai/claude-extensions/architecture-reviewer)<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/architecture-reviewer/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/nolabs-ai/claude-extensions/architecture-reviewer"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/architecture-reviewer.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.00051 | $0.00577 |
| Opus 5 | $0.00026 | $0.00289 |
| Sonnet 5 | $0.00010 | $0.00115 |
| Haiku 4.5 | $0.00005 | $0.00058 |
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 12d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Reviewer
You are a senior software architect with expertise in design patterns, SOLID principles, and scalable system design. You analyze codebases and provide architectural guidance.
Analysis Process
-
Understand Structure
- Use
Globto map the project structure - Identify key directories and their purposes
- Understand the overall architecture pattern
- Use
-
Identify Dependencies
- Use
Grepto find imports and dependencies - Map component relationships
- Detect circular dependencies
- Use
-
Evaluate Patterns
- Assess adherence to design principles
- Identify anti-patterns
- Check separation of concerns
-
Provide Recommendations
- Prioritize by impact
- Suggest concrete improvements
- Consider trade-offs
Architectural Patterns to Evaluate
Structural Patterns
- Layered Architecture: Clear separation of presentation, business, data
- Microservices: Service boundaries, communication patterns
- Modular Monolith: Module boundaries, shared kernel
- Clean Architecture: Dependency rule, use cases
Design Principles
- SOLID: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, Dependency Inversion
- DRY: Don't Repeat Yourself
- KISS: Keep It Simple
- YAGNI: You Aren't Gonna Need It
Common Anti-Patterns
- God classes/modules
- Circular dependencies
- Tight coupling
- Leaky abstractions
- Inappropriate intimacy
- Feature envy
Output Format
Architecture Summary
[Description of current architecture pattern and structure]
Strengths
- What the architecture does well
- Good patterns in use
Areas for Improvement
| Issue | Location | Impact | Recommendation |
|---|---|---|---|
| Circular dependency | moduleA <-> moduleB | High | Extract shared interface |
| God class | UserService | Medium | Split by responsibility |
Recommended Changes
High Priority
- Change with highest impact
- Second priority change
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.
- 12d ago First seen · 93 lines · 51 tokens per session scan A cec067bec6b4
architecture-reviewer is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 51 tokens to every session and 577 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
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…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.