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 skills add nWave-ai/nWave --skill nw-buddy-command-cataloggit 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/skills/nwave-ai/nwave/nw-buddy-command-catalog)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-buddy-command-catalog"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-buddy-command-catalog.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.01061 |
| Opus 5 | $0.00019 | $0.00531 |
| Sonnet 5 | $0.00008 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
nw-buddy-command-catalog 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 8d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Catalog
Wave Commands (run in order per feature)
| Command | Wave | Agent | When to Use |
|---|---|---|---|
/nw-discover |
DISCOVER | product-discoverer (Scout) | Validate problem exists, customer interviews, opportunity mapping |
/nw-diverge |
DIVERGE | diverger (Flux) | Evaluate multiple solution approaches before committing |
/nw-discuss |
DISCUSS | product-owner (Luna) | Define user stories, journeys, acceptance criteria |
/nw-design |
DESIGN | system-designer, ddd-architect, solution-architect | Route to the right architect — system (scalability), domain (DDD), or application (components) |
/nw-devops |
DEVOPS | platform-architect | CI/CD, infrastructure, observability, deployment strategy |
/nw-distill |
DISTILL | acceptance-designer | Create executable acceptance tests (Given-When-Then) |
/nw-deliver |
DELIVER | software-crafter | Full implementation: roadmap -> execute -> finalize |
Routing Commands
| Command | Purpose | When to Use |
|---|---|---|
/nw-new |
Guided wizard for new features | Starting something new — asks what you're building, recommends starting wave |
/nw-continue |
Resume in-progress feature | Returning to a feature — detects progress, starts at next wave |
/nw-fast-forward |
Run remaining waves without pausing | When you trust the agents to proceed without review between waves |
DELIVER Inner Loop Commands (manual mode)
| Command | Purpose | When to Use |
|---|---|---|
/nw-execute |
Run single roadmap step | Implementing one step at a time (learning mode) |
/nw-roadmap |
Create implementation plan | Planning steps before execution |
/nw-review |
Expert review of artifacts | Quality check on roadmap, code, or step output |
/nw-mutation-test |
Test suite effectiveness | After implementation — verifies tests catch real bugs |
/nw-finalize |
Archive completed feature | After all steps pass — creates evolution document |
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.
- 8d ago First seen · 75 lines · 39 tokens per session scan A 2e3a26911384
nw-buddy-command-catalog is a skill published in the GitHub repository nWave-ai/nWave (608 stars, last pushed 2d ago), licensed MIT. It adds 39 tokens to every session and 1,061 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 skills, from other repositories
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
engineering-workflow
A Chinese-language workflow for reliable software development. It describes exploring the problem, making a plan, using TDD (test-driven development, where tests are written before the code), debugging methodically, reviewing code, and verifying the result.
test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
story-development
Implement user stories with test-driven development methodology.
tdd
A Test-Driven Development guide. TDD means writing a failing test first, adding the smallest implementation that passes it, and then improving the code while keeping the tests passing.