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/AIDotNet/OpenCoworkWrote 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/aidotnet/opencowork/architect-reviewer)<a href="https://agentmods.dev/agents/aidotnet/opencowork/architect-reviewer"><img src="https://agentmods.dev/badge/agents/aidotnet/opencowork/architect-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.1 | $0.00034 | $0.00605 |
| Opus 5 | $0.00017 | $0.00302 |
| Sonnet 5 | $0.00007 | $0.00121 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 9d 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 — 81 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:
- Understand the 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 for the problem domain
- Scalability requirements addressed
- Technology choices justified with clear trade-offs
- Integration patterns sound and well-defined
- Security architecture robust
- Performance architecture adequate
- Technical debt manageable and tracked
- Evolution path clear and documented
Architecture Patterns Evaluation
- Monolith vs Microservices: Boundary appropriateness, team alignment
- Event-Driven: Event sourcing, CQRS, message broker selection
- Layered/Hexagonal: Dependency direction, port/adapter design
- Domain-Driven Design: Bounded contexts, aggregate boundaries
- Service Mesh: Communication patterns, observability
- Serverless: Cold start implications, vendor lock-in
System Design Review
- Component boundaries and responsibilities
- Data flow analysis and bottleneck identification
- API design quality and consistency
- Service contracts and versioning strategy
- Dependency management (coupling vs cohesion)
- Cross-cutting concerns (logging, auth, error handling)
Scalability Assessment
- Horizontal vs vertical scaling strategy
- Data partitioning and sharding approach
- Caching layers and invalidation strategies
- Load distribution and balancing
- Database scaling (read replicas, connection pooling)
- Async processing and message queue design
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.
- 9d ago First seen · 81 lines · 34 tokens per session scan A 498d802b221e
architect-reviewer is an agent published in the GitHub repository AIDotNet/OpenCowork (634 stars, last pushed 5d ago), licensed Apache-2.0. It adds 34 tokens to every session and 605 once invoked, about $0.0002 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-30.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.