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/discovergit 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/discover)<a href="https://agentmods.dev/commands/nwave-ai/nwave/discover"><img src="https://agentmods.dev/badge/commands/nwave-ai/nwave/discover.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.00024 | $0.00699 |
| Opus 5 | $0.00012 | $0.00349 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
discover 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-DISCOVER: Evidence-Based Product Discovery
Wave: DISCOVER | Agent: Scout (nw-product-discoverer)
Overview
Execute evidence-based product discovery through assumption testing and market validation. First wave in nWave (DISCOVER > DISCUSS > SPIKE > DESIGN > DEVOPS > DISTILL > DELIVER).
Scout establishes product-market fit through rigorous customer development using Mom Test interviewing principles and continuous discovery practices.
Context Files Required
- docs/project-brief.md — Initial product vision (if available)
- docs/market-context.md — Market research and competitive landscape (if available)
Previous Artifacts
None (DISCOVER is the first wave).
Wave Decisions Summary
Before completing DISCOVER, produce docs/feature/{feature-id}/discover/wave-decisions.md:
# DISCOVER Decisions — {feature-id}
## Key Decisions
- [D1] {decision}: {rationale} (see: {source-file})
## Constraints Established
- {constraint from evidence}
## Validated Assumptions
- {assumption validated by evidence, with confidence level}
## Invalidated Assumptions
- {assumption disproved, with evidence reference}
This summary enables downstream waves to quickly assess DISCOVER outcomes without reading all artifacts.
Document Update (Back-Propagation)
Not applicable (DISCOVER is the first wave — no prior documents to update).
Agent Invocation
@nw-product-discoverer
Execute *discover for {product-concept-name}.
Context Files: docs/project-brief.md (if available) | docs/market-context.md (if available)
Configuration:
- interactive: high | output_format: markdown
- interview_depth: comprehensive | evidence_standard: past_behavior
Progress Tracking
The invoked agent MUST create a task list from its workflow phases at the start of execution using TaskCreate. Each phase becomes a task with the gate condition as completion criterion. Mark tasks in_progress when starting each phase and completed when the gate passes. This gives the user real-time visibility into progress.
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 · 100 lines · 24 tokens per session scan A 3eedaa4cc2c9
discover is a command published in the GitHub repository nWave-ai/nWave (605 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 699 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
implement
Execute tasks from a track's implementation plan following TDD workflow.
run
Implement SPEC requirements using DDD/TDD methodology.
dev-tdd
Implements a feature by following the TDD (Test-Driven Development) cycle.
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).
work-quick
Quick workflow for trivial changes (1-3 files, < 50 lines, zero risk).