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/commands/nwave-ai/nwave/design)<a href="https://agentmods.dev/commands/nwave-ai/nwave/design"><img src="https://agentmods.dev/badge/commands/nwave-ai/nwave/design.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.00027 | $0.03132 |
| Opus 5 | $0.00014 | $0.01566 |
| Sonnet 5 | $0.00005 | $0.00626 |
| Haiku 4.5 | $0.00003 | $0.00313 |
Grade A, and why
design 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 today.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-DESIGN: Architecture Design
Wave: DESIGN (wave 3 of 6) | Agents: Morgan (nw-solution-architect), nw-system-designer, nw-ddd-architect, nw-platform-architect | Command: *design-architecture
Overview
Execute DESIGN wave through discovery-driven architecture design. The command routes to the right architect based on design scope: system-level (distributed architecture, scalability), domain-level (DDD, bounded contexts), or application-level (component boundaries, tech stack). Users choose an interaction mode — guided (collaborative Q&A) or propose (architect analyzes requirements and presents options with trade-offs). Analyzes existing codebase, evaluates open-source alternatives, produces C4 diagrams (Mermaid) as mandatory output.
Interactive Decision Points
Decision 0: Design Scope (MANDATORY — do NOT skip)
Question: What are you designing?
You MUST ask this question before invoking any architect. Do NOT default to application scope. The answer determines WHICH agent to invoke.
Options:
- System / infrastructure — distributed architecture, scalability, caching, load balancing, message queues → invokes @nw-system-designer
- Domain / bounded contexts — DDD, aggregates, Event Modeling, event sourcing, context mapping → invokes @nw-ddd-architect
- Application / components — component boundaries, hexagonal architecture, tech stack, ADRs → invokes @nw-solution-architect
- Full stack — all three in sequence: system -> domain -> application → invokes all three agents sequentially
- Platform / delivery infrastructure — deployment architecture, CI/CD, infrastructure as code, observability, production readiness → invokes @nw-platform-architect
Decision 1: Interaction Mode
Question: How do you want to work?
Options:
- Guide me — the architect asks questions, you make decisions together
- Propose — the architect reads your requirements and proposes 2-3 options with trade-offs
Prior Wave Consultation
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.
- today First seen · 251 lines · 27 tokens per session scan A 48b869b0384b
design is a command published in the GitHub repository nWave-ai/nWave (605 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 3,132 once invoked, about $0.0001 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-09-06.
Other commands, from other repositories
accessibility-audit
You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.
work-flow-feature
Complete workflow for developing a new feature, from exploration to merge.
work-batch
Autonomous and sequential execution of user stories from a PRD file (JSON or Markdown).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.