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.
npx agentmods add commands/nwave-ai/nwave/indexgit clone --depth 1 https://github.com/nWave-ai/nWaveWhat 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 | $0.00000 | $0.02933 |
| Opus 5 | $0.00000 | $0.01466 |
| Sonnet 5 | $0.00000 | $0.00587 |
| Haiku 4.5 | $0.00000 | $0.00293 |
Grade A, and why
index 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 3d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands
| Command | Description | Agents | Arguments |
|---|---|---|---|
/nw-buddy |
nWave concierge — ask any question about methodology, project state, commands, migration, or troubleshooting. Read-only, contextual answers. | nw-nwave-buddy | [question] - Example: "What should I do next for rate-limiting?\ |
/nw-bugfix |
Bug fix workflow: root cause analysis → user review → regression test + fix via TDD | nw-functional-software-crafter, nw-software-crafter, nw-troubleshooter | [bug-description] - Describe the defect observed |
/nw-continue |
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts. | [feature-id] - Optional: omit to auto-detect from docs/feature/ | |
/nw-deliver |
Orchestrates the full DELIVER wave end-to-end (roadmap > execute-all > finalize). Use when all prior waves are complete and the feature is ready for implementation. | nw-functional-software-crafter, nw-platform-architect, nw-software-crafter, nw-software-crafter-reviewer, nw-solution-architect, nw-troubleshooter | [feature-description] - Example: "Implement user authentication with JWT" |
/nw-design |
Designs system architecture with C4 diagrams and technology selection. Use when defining component boundaries, choosing tech stacks, or creating architecture documents. | nw-ddd-architect, nw-functional-software-crafter, nw-platform-architect, nw-software-crafter, nw-solution-architect, nw-system-designer | [component-name] - Optional: --residuality --paradigm=[auto |
/nw-devops |
Designs CI/CD pipelines, infrastructure, observability, and deployment strategy. Use when preparing platform readiness for a feature. | nw-acceptance-designer, nw-platform-architect | [deployment-target] - Optional: --environment=[staging |
/nw-diagram |
Generates C4 architecture diagrams (context, container, component) in Mermaid or PlantUML. Use when creating or updating architecture visualizations. | nw-solution-architect | [diagram-type] - Optional: --format=[mermaid |
/nw-discover |
Conducts evidence-based product discovery through customer interviews and assumption testing. Use at project start to validate problem-solution fit. | nw-product-discoverer, nw-product-owner | [product-concept] - Optional: --interview-depth=[overview |
/nw-discuss |
Conducts Jobs-to-be-Done analysis, UX journey design, and requirements gathering through interactive discovery. Use when starting feature analysis, defining user stories, or creating acceptance criteria. | nw-platform-architect, nw-product-owner, nw-solution-architect | [feature-name] - Optional: --phase=[jtbd |
/nw-distill |
Creates E2E acceptance tests in Given-When-Then format from requirements and architecture. Use when preparing executable specifications before implementation. | nw-acceptance-designer, nw-acceptance-designer-reviewer, nw-platform-architect-reviewer, nw-product-owner-reviewer, nw-software-crafter, nw-solution-architect-reviewer | [story-id] - Optional: --test-framework=[cucumber |
/nw-diverge |
Generates 3-5 divergent design directions through JTBD analysis, competitive research, structured brainstorming, and taste evaluation before convergence. | nw-diverger, nw-diverger-reviewer, nw-product-owner, nw-researcher | [feature-id] - Optional: --work-type=[new-product |
/nw-document |
Creates evidence-based documentation following DIVIO/Diataxis principles. Use when writing tutorials, how-to guides, reference docs, or explanations. | nw-documentarist, nw-documentarist-reviewer, nw-researcher, nw-researcher-reviewer | [topic/component] - Optional: --type=[tutorial |
/nw-execute |
Use when a DELIVER roadmap already exists and you need to dispatch exactly one identified step through its TDD cycle. Use nw-roadmap to create the plan, nw-deliver for the whole wave, and nw-continue to resume at the next inferred step. | nw-researcher, nw-software-crafter | [agent] [feature-id] [step-id] - Example: @nw-software-crafter "auth-upgrade" "01-01" |
/nw-fast-forward |
Fast-forwards through remaining waves end-to-end without stopping for review between waves. | [feature-description] - Optional: --from=[discuss | |
/nw-finalize |
Archives a completed feature to docs/evolution/, migrates lasting artifacts to permanent directories, and cleans up the temporary workspace. Use after all implementation steps pass and mutation testing completes. | nw-acceptance-designer, nw-platform-architect, nw-product-owner, nw-researcher, nw-software-crafter, nw-solution-architect | [agent] [feature-id] - Example: @platform-architect "auth-upgrade" |
/nw-forge |
Creates new specialized agents using the 5-phase workflow (ANALYZE > DESIGN > CREATE > VALIDATE > REFINE). Use when building a new AI agent or validating an existing agent specification. | nw-agent-builder | [agent-name] - Optional: --type=[specialist |
/nw-hotspot |
Git change frequency hotspot analysis — find the most-changed files in your codebase | [--top=N] [--since=6m] [--json] [--rank report.md] [--detail file] | |
/nw-mikado |
[EXPERIMENTAL] Complex refactoring roadmaps with visual tracking | nw-software-crafter | [refactoring-goal] - Optional: --complexity=[simple |
/nw-mutation-test |
Runs feature-scoped mutation testing to validate test suite quality. Use after implementation to verify tests catch real bugs (kill rate >= 80%). | nw-software-crafter | [feature-id] - Optional: --threshold=[75 |
/nw-new |
Guided wizard to start a new feature. Asks what you want to build, recommends the right starting wave, and launches it. | [feature-description] - Example: "Add rate limiting to the API gateway" | |
/nw-optimize-tests |
Minimizes test count while preserving coverage. Detects byte-identical pairs, parametrize-inflation, language-guarantee tests, AST-shape tests, stale migration nets. Approval gate before any change. | nw-test-optimizer, nw-test-optimizer-reviewer | [scope] - Optional: a path (e.g. tests/des/unit/), a feature-id (auto-resolves to tests//), or omit for full unit suite. --reviewer to chain reviewer agent. |
/nw-refactor |
Applies the Refactoring Priority Premise (RPP) levels L1-L6 for systematic code refactoring. Use when improving code quality through structured refactoring passes. | nw-software-crafter | [target-class-or-module] - Optional: --level=[1-6] --method=[extract |
/nw-research |
Gathers knowledge from web and files, cross-references across multiple sources, and produces cited research documents. Use when investigating technologies, patterns, or decisions that need evidence backing. | nw-researcher | [topic] - Optional: --research_depth=[overview |
/nw-review |
Dispatches an expert reviewer agent to critique workflow artifacts. Use when a roadmap, implementation, or step needs quality review before proceeding. | nw-platform-architect, nw-platform-architect-reviewer, nw-software-crafter, nw-software-crafter-reviewer, nw-solution-architect, nw-solution-architect-reviewer | [agent] [artifact-type] [artifact-path] - Example: @software-crafter task "roadmap.json" |
/nw-rigor |
Selects a quality-vs-token-consumption profile (lean, standard, thorough, exhaustive, custom, inherit) and persists it globally (~/.nwave/global-config.json) or per-project (.nwave/des-config.json). Use when tuning how much rigor wave commands apply. | [profile] - Optional: lean, standard, thorough, exhaustive, custom, inherit. Omit for interactive selection. | |
/nw-roadmap |
Creates a phased roadmap.json for a feature goal with acceptance criteria and TDD steps. Use when planning implementation steps before execution. | nw-product-owner, nw-software-crafter, nw-solution-architect | [agent] [goal-description] - Example: @solution-architect "Migrate to microservices" |
/nw-root-why |
Root cause analysis and debugging | nw-troubleshooter | [problem-description] - Optional: --depth=[3 |
/nw-spike |
Runs a timeboxed spike to validate one core assumption before DESIGN. Use after DISCUSS when the feature involves a new mechanism, performance requirement, or external integration. | nw-software-crafter, nw-solution-architect | [feature-description] - Example: "wave-matrix -- derive feature status from pytest + filesystem\ |
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.
- 3d ago First seen · 33 lines · 0 tokens per session scan A 3f88bed30691
index is a command published in the GitHub repository nWave-ai/nWave (602 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,933 tokens. 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 commands, from other repositories
sdlc-build
Phase 2 — Build. Reads plan-handoff.md, optionally runs ux-designer (hasui gate), then loops fullstack-engineer over each slice with ralph-loop self-correction, then runs qa-engineer for E2E tests.
sdlc-implement
Standalone issue implementation with Ralph Loop — implements a single Linear issue or free-form spec using fullstack-engineer + self-correcting retry loop.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
sdlc-operate
Phase 5 — Operate. Runs sre-engineer always + data-engineer when hasdatapipeline is true. Reads ship-handoff.md for clean context.
to-issues
Create one Linear issue per slice from an existing scope.json. Run standalone to (re)create issues without rerunning the full Plan phase. Falls back to docs/issues.md if Linear MCP is unavailable.
to-prd
Synthesize a PRD from an existing grill-summary.md + scope.json. Run standalone when you already have Plan phase artifacts and want to (re)generate the PRD without rerunning the full interview.