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-opportunity-mappinggit 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-opportunity-mapping)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-opportunity-mapping"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-opportunity-mapping/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-opportunity-mapping"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-opportunity-mapping.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.00025 | $0.00861 |
| Opus 5.5 | $0.00010 | $0.00344 |
| Sonnet 5.5 | $0.00005 | $0.00172 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
nw-opportunity-mapping 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 1mo 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Opportunity Mapping
Opportunity Solution Tree (OST)
Connects desired outcomes to opportunities to solution ideas:
Desired Outcome
|
+-- Opportunity 1 (score)
| +-- Solution Idea A
| +-- Solution Idea B
|
+-- Opportunity 2 (score)
| +-- Solution Idea C
|
+-- Opportunity 3 (score)
+-- Solution Idea D
+-- Solution Idea E
Building the OST
- Define desired outcome from customer research
- Map opportunities from interview insights (min 5 distinct)
- Score each using Opportunity Algorithm
- Generate solution ideas for top 2-3
- Seek real diversity in solutions (avoid variations of same idea)
Opportunity Scoring Algorithm
Formula: Score = Importance + Max(0, Importance - Satisfaction) Importance: 1-10 | Satisfaction: 1-10 | Max score: 20
| Score | Meaning | Action |
|---|---|---|
| >8 | High importance, satisfaction gap -- underserved | Pursue |
| 5-8 | Moderate importance or partially served | Evaluate |
| <5 | Low importance or well-served | Deprioritize |
Process: gather importance + satisfaction from 5+ interviews, calculate per opportunity, rank, select top 2-3.
Job Mapping (JTBD)
Universal Job Map Steps
| Step | Goal | Outcome Format |
|---|---|---|
| Define | Determine what needs doing | Minimize time to identify [object] |
| Locate | Find inputs/information | Minimize time to gather [resources] |
| Prepare | Ready inputs for use | Minimize likelihood of missing [requirements] |
| Confirm | Verify readiness | Minimize likelihood of incorrect [categorization] |
| Execute | Perform core task | Minimize time from [start] to [completion] |
| Monitor | Track progress | Minimize uncertainty about [status] |
| Modify | Adjust if needed | Minimize effort to correct [issues] |
| Conclude | Complete the job | Minimize time from [completion] to [result] |
Outcome statement format: [Direction] + [Metric] + [Object] + [Clarifier] Example: "Minimize the time it takes to identify which project budget a new expense should be allocated to"
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.
- 1mo ago First seen · 99 lines · 25 tokens per session scan A a143185ccd6d
nw-opportunity-mapping is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 861 once invoked, about $0.0001 per session on Opus 5.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
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.
tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
moai-run
Implement SPEC requirements using DDD/TDD methodology.
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.