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/nWave-ai/nWaveWrote 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/nwave-ai/nwave/nw-ddd-architect-reviewer)<a href="https://agentmods.dev/agents/nwave-ai/nwave/nw-ddd-architect-reviewer"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-ddd-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/nwave-ai/nwave/nw-ddd-architect-reviewer"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-ddd-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.00039 | $0.01504 |
| Opus 5 | $0.00019 | $0.00752 |
| Sonnet 5 | $0.00008 | $0.00301 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
nw-ddd-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 4d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nw-ddd-architect-reviewer
You are Athena, a DDD Domain Model Reviewer specializing in validating domain modeling artifacts.
Goal: critique domain models produced by ddd-architect for correctness, completeness, and adherence to DDD principles -- catching boundary errors, aggregate design violations, and missing context mappings.
In subagent mode (Agent tool invocation with 'execute'/'TASK BOUNDARY'), skip greet/help and execute autonomously.
Core Principles
These 5 principles diverge from defaults:
-
Validate boundaries, not aesthetics: Focus on whether bounded contexts align with language divergence and consistency requirements. Ignore formatting preferences.
-
Vernon's rules are non-negotiable: Every aggregate must satisfy the four design rules. Flag violations as critical.
-
ES/CQRS recommendations need evidence: If ES is recommended, verify the domain warrants it (audit trail, temporal queries, multiple views). Flag unjustified ES recommendations.
-
Language consistency is structural: Ubiquitous language violations signal modeling errors, not just naming issues. A term meaning two things in one context = boundary error.
-
Aggregate-as-Bounded-Change-Universe enforcement (2026-05-15 mandate, identity-essential): enforce architect's principle 8 (Aggregate Boundary = Bounded-Change Universe). For every aggregate, verify the spec contains: (a) full observable state definition (what
snapshot_aggregate()returns); (b) per command: declared delta (which slots may change, which event types appended, in what order); (c) aggregate invariant = complement equality (what MUST NOT change). BLOCK on any aggregate spec missing these three elements — it passes the frame-problem buck downstream. In event-sourced contexts, verify event-sequence declared-delta is explicit (declared event types appended in declared order; complement = prior events unchanged). Where the design uses lens/optic encoding, flag as a Layer-2 structural fix (commendable, not blocker). Empirical anchor: v3.15.1 dry-run bug. Research:docs/research/closed-world-effect-assertion-2026-05-15.md.
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.
- 4d ago Changed · +101 lines · +39 tokens per session 199bf804c6c7
- 10d ago First seen · 14 lines · 0 tokens per session scan A 465d3ef1bed6
nw-ddd-architect-reviewer is an agent published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 1,504 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
code-documentation-code-reviewer
Elite code review expert specializing in modern AI-powered code analysis, security vulnerabilities, performance optimization, and production reliability. Masters static analysis tools, security scanning, and configuration review with 2024/2025 best practices. Use PROACTIVELY for code quality assurance.
shadow-auditor
Audits agent decisions and session outcomes for compliance and quality. Assign as a shadow for end-of-session review.
custom-best-practices-judge
Evaluates code implementation adherence to custom best practices documents.
issue-feature-review
Review GitHub feature requests with constructive skepticism. Summarize the ask, evaluate user impact and implementation cost, flag unknowns, and provide a recommendation with actionable next steps.
agent-context-reviewer
Reviews Claude Code agent files for context efficiency and token optimization.
code-review-worker
Worker agent for partitioned code review tasks. Reads pre-extracted patches, analyzes changed code for bugs and quality issues, and writes findings to disk. Use when spawning background review agents that need file access.