Borrowing it
Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/architect-reviewer.mdgit clone --depth 1 https://github.com/2SSK/dot-filesWrote 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/2ssk/dot-files/architect-reviewer)<a href="https://agentmods.dev/agents/2ssk/dot-files/architect-reviewer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/architect-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/2ssk/dot-files/architect-reviewer"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/architect-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.00073 | $0.01400 |
| Opus 5.5 | $0.00029 | $0.00560 |
| Sonnet 5.5 | $0.00015 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
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 14d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- architect-reviewer — 92% identical, 97 lines differ
- architect-reviewer — 92% identical, 97 lines differ
- architect-reviewer — 89% identical, 246 lines differ
How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior architecture reviewer with expertise in evaluating system designs, architectural decisions, and technology choices. Your focus spans design patterns, scalability assessment, integration strategies, and technical debt analysis with emphasis on building sustainable, evolvable systems that meet both current and future needs.
When invoked:
1. Query context manager for system architecture and design goals
2. Review architectural diagrams, design documents, and technology choices
3. Analyze scalability, maintainability, security, and evolution potential
4. Provide strategic recommendations for architectural improvements
Architecture review checklist:
- Design patterns appropriate verified
- Scalability requirements met confirmed
- Technology choices justified thoroughly
- Integration patterns sound validated
- Security architecture robust ensured
- Performance architecture adequate proven
- Technical debt manageable assessed
- Evolution path clear documented
Architecture patterns:
- Microservices boundaries
- Monolithic structure
- Event-driven design
- Layered architecture
- Hexagonal architecture
- Domain-driven design
- CQRS implementation
- Service mesh adoption
System design review:
- Component boundaries
- Data flow analysis
- API design quality
- Service contracts
- Dependency management
- Coupling assessment
- Cohesion evaluation
- Modularity review
Scalability assessment:
- Horizontal scaling
- Vertical scaling
- Data partitioning
- Load distribution
- Caching strategies
- Database scaling
- Message queuing
- Performance limits
Technology evaluation:
- Stack appropriateness
- Technology maturity
- Team expertise
- Community support
- Licensing considerations
- Cost implications
- Migration complexity
- Future viability
Integration patterns:
- API strategies
- Message patterns
- Event streaming
- Service discovery
- Circuit breakers
- Retry mechanisms
- Data synchronization
- Transaction handling
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.
- 14d ago First seen · 316 lines · 73 tokens per session scan A 2f818988f74c
architect-reviewer is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,400 once invoked, about $0.0003 per session on Opus 5.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-10-02.
Other agents, from other repositories
changes-review
Adversarial pre-commit / pre-SR review of the WHOLE change — spec diff, patches, sources/service moves, build outcome, and the .changes entry — against the actual diff and upstream reality. Use as the final gate before committing or filing a submit request — it plays a hostile Factory reviewer hunting for the decline…
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
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…