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-persona-jtbd-analysisgit 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-persona-jtbd-analysis)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-persona-jtbd-analysis"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-persona-jtbd-analysis/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-persona-jtbd-analysis"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-persona-jtbd-analysis.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.00039 | $0.01093 |
| Opus 5.5 | $0.00016 | $0.00437 |
| Sonnet 5.5 | $0.00008 | $0.00219 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
nw-persona-jtbd-analysis 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona and JTBD Analysis
Use during Phase 1 (GATHER) when the user lacks clear personas or the "Who" section needs rigorous definition. Provides structured alternative to ad-hoc persona descriptions.
Persona Template
For each user type, build a complete persona:
## Persona: {Name}
**Who**: {Role description -- one sentence capturing relationship to product}
**Demographics**:
- {Characteristic 1: e.g., technical proficiency level}
- {Characteristic 2: e.g., frequency of interaction}
- {Characteristic 3: e.g., environment/context of use}
- {Characteristic 4: e.g., primary motivation}
**Jobs-to-be-Done**: (see Job Step Table below)
**Pain Points**:
- {Pain 1} -- maps to Job Step: {step name}
- {Pain 2} -- maps to Job Step: {step name}
**Success Metrics**:
- {Quantified outcome 1: e.g., "Task completed in < 2 minutes"}
- {Quantified outcome 2: e.g., "Zero manual configuration steps"}
Job Step Table
Each persona has job steps describing what they accomplish. Steps follow ODI format.
| Job Step | Goal | Desired Outcome |
|---|---|---|
| {Verb} | {What the user wants to achieve} | Minimize {metric} of {undesirable state} |
Rules for Job Steps
- Job Steps are always verbs: Discover, Validate, Install, Configure, Monitor, Recover
- Goals describe what the user wants, not what the system does
- Desired Outcomes use ODI format: "Minimize [time/effort/risk/likelihood] of [undesirable state]"
- Each step maps to a workflow point where value is created or destroyed
Example Job Step Table
| Job Step | Goal | Desired Outcome |
|---|---|---|
| Discover | Find the right tool for the task | Minimize time to evaluate fit |
| Install | Get the tool running locally | Minimize steps to working state |
| Configure | Adapt to local environment | Minimize likelihood of misconfiguration |
| Verify | Confirm correct installation | Minimize uncertainty about readiness |
| Start | Begin productive work | Minimize time from install to first output |
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 · 116 lines · 39 tokens per session scan A 0bfd73c58c4a
nw-persona-jtbd-analysis is a skill published in the GitHub repository nWave-ai/nWave (620 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 1,093 once invoked, about $0.0002 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.