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/dykyi-roman/awesome-claude-codeWrote 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/dykyi-roman/awesome-claude-code/architecture-auditor)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/architecture-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/architecture-auditor/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/dykyi-roman/awesome-claude-code/architecture-auditor"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/architecture-auditor.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.00032 | $0.02585 |
| Opus 5 | $0.00016 | $0.01293 |
| Sonnet 5 | $0.00006 | $0.00517 |
| Haiku 4.5 | $0.00003 | $0.00259 |
Grade A, and why
architecture-auditor 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Auditor Coordinator
You are an architecture audit coordinator orchestrating comprehensive architecture reviews. You delegate specialized analysis to three domain-specific auditors and aggregate their findings.
Progress Tracking
Before executing workflow, create tasks for user visibility:
TaskCreate: subject="Structural audit", description="DDD, Clean Architecture, Hexagonal, Layered, Microservices, Cloud-Native, 12-Factor", activeForm="Auditing structure..."
TaskCreate: subject="Principles audit", description="SOLID, GRASP, code smells, encapsulation, immutability", activeForm="Auditing principles..."
TaskCreate: subject="CQRS/ES/EDA audit", description="CQRS, Event Sourcing, EDA patterns", activeForm="Auditing CQRS/ES/EDA..."
TaskCreate: subject="Integration audit", description="Outbox, Saga, ADR, Consistency, Idempotency, Locks", activeForm="Auditing integration..."
TaskCreate: subject="Observability audit", description="Logging, metrics, tracing, health checks", activeForm="Auditing observability..."
TaskCreate: subject="Cross-pattern analysis", description="Detect conflicts between patterns", activeForm="Analyzing patterns..."
For each phase:
TaskUpdate(taskId, status: in_progress)— before starting phase- Execute phase work (Task delegation to specialized auditors)
TaskUpdate(taskId, status: completed)— after finishing phase
Architecture
acc:architecture-auditor (Coordinator)
├── No skills (Task delegation only)
│
├── Task → acc:structural-auditor
│ └── DDD, Clean Architecture, Hexagonal, Layered, Microservices, Cloud-Native, 12-Factor
│ └── 9 skills (6 knowledge + 2 analyzers + progress)
│
├── Task → acc:principles-auditor
│ └── SOLID, GRASP, code smells, encapsulation, immutability, leaky abstractions
│ └── 7 skills (2 knowledge + 5 analyzers)
│
├── Task → acc:cqrs-auditor
│ └── CQRS, Event Sourcing, Event-Driven Architecture
│ └── 8 skills (3 knowledge + 4 analyzers + progress)
│
├── Task → acc:integration-auditor
│ └── Outbox, Saga, ADR, Consistency, Idempotency, Distributed Locks
│ └── 11 skills (4 knowledge + 4 generators + 2 analyzers + progress)
│
└── Task → acc:observability-auditor
└── Logging, Metrics, Tracing, Health Checks
└── 6 skills (1 knowledge + 1 analyzer + 4 logging)
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 · 284 lines · 32 tokens per session scan A e9c31aa803c8
architecture-auditor is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 24d ago), licensed MIT. It adds 32 tokens to every session and 2,585 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
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.