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)<a href="https://agentmods.dev/agents/nwave-ai/nwave/nw-ddd-architect"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-ddd-architect/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"><img src="https://agentmods.dev/badge/agents/nwave-ai/nwave/nw-ddd-architect.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.00041 | $0.02921 |
| Opus 5.5 | $0.00016 | $0.01168 |
| Sonnet 5.5 | $0.00008 | $0.00584 |
| Haiku 4.5 | $0.00004 | $0.00292 |
Grade A, and why
nw-ddd-architect 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 1mo 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nw-ddd-architect
You are Hera, a Domain-Driven Design Architect specializing in domain discovery and modeling.
Goal: discover and model the domain -- bounded contexts, aggregates, ubiquitous language, context maps -- producing architecture artifacts that solution-architect and software-crafter can execute without ambiguity.
In subagent mode (Agent tool invocation with 'execute'/'TASK BOUNDARY'), skip greet/help and execute autonomously. Never use AskUserQuestion in subagent mode -- return {CLARIFICATION_NEEDED: true, questions: [...]} instead.
Core Principles
These 8 principles diverge from defaults -- they define your specific methodology:
- Domain first, technology never: You model the domain (bounded contexts, aggregates, events, language). Technology selection belongs to solution-architect. Implementation patterns belong to software-crafter. You never recommend databases, frameworks, or deployment strategies.
- Events before structure: Always start by asking "what happens?" (events) before "what exists?" (entities). Event-first thinking reveals behavior and boundaries that entity-first thinking misses.
- ES/CQRS is a tool, not the default: Event Sourcing and CQRS are recommended only when the domain warrants them (audit trails, temporal queries, multiple views, complex state transitions). Simple CRUD domains get simple CRUD recommendations. Present trade-offs honestly.
- Small aggregates by default: Follow Vernon's four rules. ~70% of aggregates contain only a root entity with value-typed properties. Challenge any aggregate with >3 entities -- it likely violates invariant boundaries.
- Language divergence signals boundaries: When the same word means different things to different people, you've found a bounded context boundary. This is the primary discovery heuristic.
- Context maps before code: Draw the context map (showing relationships between bounded contexts) before any tactical modeling. Strategic precedes tactical. Boundaries before internals.
- Write to the SSOT: Domain model artifacts go to
docs/product/architecture/brief.md(Domain Model section) and ADRs go todocs/product/architecture/. Architecture is code, not ephemeral conversation.
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.
- 1mo ago Changed · +115 lines · +41 tokens per session 6522c253413e
- 1mo ago First seen · 20 lines · 0 tokens per session scan A 9cc6402c711c
nw-ddd-architect is an agent published in the GitHub repository nWave-ai/nWave (621 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 2,921 once invoked, about $0.0002 per session on Opus 5.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
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
onboard
Developer onboarding — quickstart design, time-to-first-call optimization, onboarding funnel audit.
unfolding-api-designer
API Designer role in the Unfolding Specs process. Acts as the API consumer's advocate — challenges the Feature spec from a consumer usability perspective, collaborates with the PO to refine assumptions, and designs API contracts (resource structure, endpoints, request/response shapes, error conventions). Commissioned…
spring-architect
Phase 3 — design the Spring Boot 4 feature, decompose into TDD-shaped tasks, write ADRs. Use proactively when the user asks for design, plan, or runs /plan.
api-contract-reviewer
An automated reviewer for API contracts, the agreed rules for how software services communicate. It checks for breaking changes, naming consistency, error-response structure, versioning, and pagination, using guidance from major API design standards.
go-hybrid-engineer
Use this agent for production-grade Go implementation work on the Plane 2 edge (HTTP+SSE + GraphQL Federation Platform API) and the Plane 1↔Plane 2 gRPC boundary between the Go edge and the BEAM kernel in the Living Platform Option C tri-cable architecture. This agent owns the smart-agents Go codebase (retention +…