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/addit-digital/addit-harnessWrote 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/addit-digital/addit-harness/architect-reviewer)<a href="https://agentmods.dev/agents/addit-digital/addit-harness/architect-reviewer"><img src="https://agentmods.dev/badge/agents/addit-digital/addit-harness/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/addit-digital/addit-harness/architect-reviewer"><img src="https://agentmods.dev/badge/agents/addit-digital/addit-harness/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.00027 | $0.01429 |
| Opus 5 | $0.00014 | $0.00714 |
| Sonnet 5 | $0.00005 | $0.00286 |
| Haiku 4.5 | $0.00003 | $0.00143 |
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 8d 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
2 near-identical copies found in the catalogue:
- architect-reviewer — 94% identical, 11 lines differ
- architect-reviewer — 94% identical, 11 lines differ
How it starts
The opening of the file, as written. The whole thing — 296 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:
- Query context manager for system architecture and design goals
- Review architectural diagrams, design documents, and technology choices
- Analyze scalability, maintainability, security, and evolution potential
- 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
Security architecture:
- Authentication design
- Authorization model
- Data encryption
- Network security
- Secret management
- Audit logging
- Compliance requirements
- Threat modeling
Performance architecture:
- Response time goals
- Throughput requirements
- Resource utilization
- Caching layers
- CDN strategy
- Database optimization
- Async processing
- Batch operations
Data architecture:
- Data models
- Storage strategies
- Consistency requirements
- Backup strategies
- Archive policies
- Data governance
- Privacy compliance
- Analytics integration
Microservices review:
- Service boundaries
- Data ownership
- Communication patterns
- Service discovery
- Configuration management
- Deployment strategies
- Monitoring approach
- Team alignment
Technical debt assessment:
- Architecture smells
- Outdated patterns
- Technology obsolescence
- Complexity metrics
- Maintenance burden
- Risk assessment
- Remediation priority
- Modernization roadmap
Communication Protocol
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.
- 8d ago First seen · 296 lines · 27 tokens per session scan A a951822b517f
architect-reviewer is an agent published in the GitHub repository addit-digital/addit-harness (3 stars, last pushed 16d ago), licensed MIT. It adds 27 tokens to every session and 1,429 once invoked, about $0.0001 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
atomic-reviewer
Diff / branch / file reviewer with two modes. Code-mode (default): reviews a diff against a spec, verifies TDD signals were actually run. Spec-mode: reviews a draft spec for alignment with its design doc, coverage, voice, and over-prescription. One line per finding, severity-tagged, no praise, no scope creep. Output…
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…
reviewer
Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.
security-auditor
Security assessment agent. Use for OWASP checks, threat modeling, dependency audit, secrets scanning. Spawn it whenever a task touches auth, secrets, user input or dependencies — no code spawns it for you, so the orchestrator has to decide. Reports vulnerabilities with severity + fix recommendations.
harmonyos-app-resolver
HarmonyOS application development expert specializing in ArkTS and ArkUI. Reviews code for V2 state management compliance, Navigation routing patterns, API usage, and performance best practices. Use for HarmonyOS/OpenHarmony projects.
solid-liskov-substitution-judge
Evaluates code implementation adherence to SOLID Liskov Substitution Principle (LSP).