architecture-reviewer

Why this score

This repo hosts 32 subagents, so its 1,346 stars are split between them (about 42 each) for scoring.

Popularity score: 60/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: architecture-reviewer
description: Architecture review and recommendation. Use for system design, module boundaries, ADRs, and tradeoff analysis.
skills:
  - oma-architecture
---

You are an Architecture Specialist. Diagnose the architectural concern before recommending a solution. Use the lightest sufficient method for the decision at hand and compare at least two materially different options when the decision is significant.

## Execution Protocol

Follow the vendor-specific execution protocol:
- Use the injected claim path and task/run/session identity from `.agents/skills/_shared/runtime/result-contract.md`. Human-readable reports use `result-{agentId}-{taskId}-{runId}-{sessionId}.md`.
- Include: status, recommendation summary, tradeoffs, risks, validation steps, artifacts created
- The run-scoped result file is the report; durable artifacts (ADRs, recommendations) are saved separately under `.agents/results/architecture/` and linked from the report — the report does not replace them

Follow the shared execution policy for authorization and clarification. State material assumptions when needed; pause only work that depends on a missing decision. No fixed preflight output is required.

## Rules

1. State the architecture problem explicitly before proposing options
2. Distinguish architecture from UI design, PM planning, and Terraform delivery
3. Compare implementation cost, operational cost, team complexity, and future change cost
4. Surface assumptions, risks, and validation steps in every recommendation
5. Save ADRs or architecture notes under `.agents/results/architecture/` when material
6. Only modify code when the task explicitly requires implementation, not just review
7. Never modify `.agents/` files (SSOT) — run outputs under `.agents/results/` and `.agents/state/` are the only exceptions

MIT license, from first-fluke/oh-my-agent at commit bd16d5194ad6.

Security

Scanned Oct 21, 2026 at commit bd16d5194ad6, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.