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-divergegit 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-diverge)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-diverge"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-diverge/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/skills/nwave-ai/nwave/nw-diverge"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-diverge.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01966 |
| Opus 5 | $0.00023 | $0.00983 |
| Sonnet 5 | $0.00009 | $0.00393 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
nw-diverge 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 6d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NW-DIVERGE: Structured Divergent Thinking Before Convergence
Wave: DIVERGE (between DISCOVER and DISCUSS, optional) | Agent: Flux (nw-diverger) | Command: /nw-diverge
Overview
Execute DIVERGE wave through Flux's 4-phase workflow: JTBD analysis|competitive research|structured brainstorming|taste-filtered evaluation. Transforms a validated problem into 3-5 concrete, taste-scored design directions so DISCUSS can converge on one with confidence.
DIVERGE is optional. Brownfield features with a clear direction may skip it (see skip checklist in design spec). New products and pivot decisions benefit most from structured divergence.
Interactive Decision Points
Decision 1: Work Type
Question: What type of work is this? Options:
- New product -- no prior solution exists, full divergence needed
- Brownfield feature -- existing product, exploring approach alternatives
- Pivot / redesign -- existing feature being reconsidered from scratch
- Other -- user provides custom context
Decision 2: Research Depth
Question: How deep should competitive research go? Options:
- Lightweight -- 3 competitors, known market
- Comprehensive -- 5+ competitors including non-obvious alternatives
- Deep-dive -- cross-category research, adjacent markets, academic references
Prior Wave Consultation
Before beginning DIVERGE work, read SSOT and prior wave artifacts:
- SSOT (if
docs/product/exists):docs/product/jobs.yaml-- validated jobs and opportunity scoresdocs/product/vision.md-- product vision and strategic context
- Project context:
docs/project-brief.md|docs/stakeholders.yaml(if available) - DISCOVER artifacts: Read
docs/feature/{feature-id}/discover/(if present)wave-decisions.md-- validated assumptions and key decisionsproblem-validation.md-- customer evidence grounding the problem
Migration gate: If docs/product/ does not exist but docs/feature/ has existing features, STOP. Guide the user to docs/guides/migrating-to-ssot-model/README.md and complete the migration first. If greenfield, DIVERGE will bootstrap docs/product/jobs.yaml with the validated job.
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.
- 6d ago First seen · 164 lines · 45 tokens per session scan A 70b9da265d91
nw-diverge is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 1,966 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-09-03.
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.
form-design
Design a form end to end — field order, grouping, validation, and completion. Use when the artifact is a form. For product-wide error strategy use error-handling-ux; for first-run signup use onboarding-design.
peak-end-rule
Apply the Peak-End Rule — a flow is remembered by its most intense moment and its last. Use when designing completion, celebration, or cancellation moments. For sustaining engagement mid-flow, use zeigarnik-effect.
law-of-similarity
Apply the Law of Similarity — shared colour, shape, or size signals that elements belong to one category. Use when signalling relationships across distance. For grouping by position, use law-of-proximity.
law-of-common-region
Apply the Law of Common Region — a shared container, background, or border groups elements regardless of spacing. Use when grouping must survive a tight layout. For grouping by spacing alone, use law-of-proximity.
concept-selection
Choose between competing concepts against criteria fixed in advance, and record what each rejected concept was testing. Use when several directions are alive and one has to win. For picking which problem to work on, use opportunity-framework (ux-strategy); for deciding by production traffic, use a-b-test-design.