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-jtbd-coregit 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-jtbd-core)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-jtbd-core"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-jtbd-core/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-jtbd-core"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-jtbd-core.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.00042 | $0.02207 |
| Opus 5 | $0.00021 | $0.01104 |
| Sonnet 5 | $0.00008 | $0.00441 |
| Haiku 4.5 | $0.00004 | $0.00221 |
Grade A, and why
nw-jtbd-core 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JTBD Core Theory
Jobs-to-be-Done reframes product development around the progress customers seek rather than products they buy. Customers "hire" products to accomplish specific jobs. The job exists independently of any solution.
The Three Job Dimensions
Every job has three dimensions. Capture all three during discovery -- functional jobs surface first, but emotional and social jobs drive switching decisions.
Functional: Practical task to accomplish. Measurable, concrete, articulated first.
- "Deploy a new feature to production without downtime"
- "Identify the root cause of a performance regression"
Emotional: How the customer wants to feel (or avoid feeling). Internal, personal, often unarticulated.
- "Feel confident that my changes will not break production"
- "Feel in control of the project timeline despite changing requirements"
Social: How the customer wants to be perceived. Identity, status, professional reputation.
- "Be seen as a technically competent lead who makes sound decisions"
- "Demonstrate to stakeholders that the team delivers measurable value"
Discovery Questions by Dimension
| Dimension | Questions |
|---|---|
| Functional | "What were you trying to accomplish?" / "Walk me through what you did." |
| Emotional | "How did that make you feel?" / "What were you worried about?" |
| Social | "Who else was involved or affected?" / "What would others think?" |
Job Story Format
Job stories emphasize situation and motivation rather than persona and action.
When [situation/context],
I want to [motivation/capability],
so I can [expected outcome/benefit].
Writing Tips
- Refine situation with context: "When I am nearly done with a document" beats "When I want to save a document"
- Focus on job, not task: Job is the higher-level goal; task is one possible way to achieve it
- Specify motivation, not implementation: "I want to be confident my work is saved" not "I want a save button"
- Leave design space open: Job stories do not prescribe solutions
- Reveal the forces: Story should hint at push (frustration), pull (desire), anxiety (risk), habit (comfort)
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 · 232 lines · 42 tokens per session scan A 2ba49cb0a45d
nw-jtbd-core is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 5d ago), licensed MIT. It adds 42 tokens to every session and 2,207 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
tutorial
Interactive tutorial teaching Ouroboros hands-on.
animation
Author animated technical explainer diagrams as .anim.json files for Nimbalyst's Animation editor. Use when the user wants to animate a diagram, show how a system/protocol/algorithm behaves over time, build a motion explainer, or turn a static architecture diagram into something that plays.
subscription-setup
A setup workflow for creating recurring medical-learning subscriptions after a doctor’s profile has been registered.
exam-material-recommendation
A study-material recommendation tool for doctors preparing for professional exams or job-related training. It uses the person’s target, timeline, available study time, and specialty, while treating the official exam syllabus as the main reference.
moai-workflow-jit-docs
Enhanced Just-In-Time document loading system that discovers, loads, and caches relevant documentation based on user intent and project context. Use when users need specific documentation on demand.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.