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-bdd-integrationgit 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-bdd-integration)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-jtbd-bdd-integration"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-jtbd-bdd-integration/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-bdd-integration"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-jtbd-bdd-integration.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.02309 |
| Opus 5 | $0.00023 | $0.01154 |
| Sonnet 5 | $0.00009 | $0.00462 |
| Haiku 4.5 | $0.00005 | $0.00231 |
Grade A, and why
nw-jtbd-bdd-integration 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 7d 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JTBD to BDD Integration
Use when translating JTBD discoveries (job stories, forces, job map) into testable BDD scenarios. Job stories map naturally to Given-When-Then because both emphasize context (situation/given), action (motivation/when), and outcome (result/then).
Job Story to Given-When-Then Translation
The Pattern
Job Story:
When [situation],
I want to [motivation],
so I can [outcome].
BDD Scenario:
Given [the situation from the job story]
When [user takes action aligned with the motivation]
Then [the outcome is achieved and measurable]
Worked Example
Job Story: "When I receive an alert that a production service is degraded, I want to see the most likely root cause with supporting evidence, so I can begin remediation within minutes instead of hours."
Scenario: Root cause surfaced from degradation alert
Given the monitoring system has detected degraded response times on the payment service
And the degradation started 5 minutes ago
When the operator opens the incident dashboard
Then the system displays the top 3 probable root causes ranked by likelihood
And each root cause includes supporting metrics and log evidence
And the most likely root cause is displayed within 10 seconds
Scenario: Remediation guidance from identified root cause
Given the operator has identified the root cause as database connection pool exhaustion
When the operator selects the recommended remediation action
Then the system presents a runbook with step-by-step instructions
And the estimated time to remediate is displayed
And the operator can execute the first step directly from the dashboard
Translation Rules
- Given = situation from job story, made concrete with specific data
- When = user action fulfilling the motivation
- Then = measurable outcome, including quality attributes (time, confidence, completeness)
Multi-Scenario Expansion
One job story typically produces 3-5 BDD scenarios:
- Happy path: Outcome achieved as described
- Anxiety path: User's fear about new solution addressed
- Habit path: User transitioning from old workflow supported
- Edge cases: Derived from job map steps (see below)
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.
- 7d ago First seen · 250 lines · 45 tokens per session scan A 465609255610
nw-jtbd-bdd-integration is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 2,309 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.
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.
behavior-contract
Bug condition/postcondition formalization as testable Behavior Contracts. Defines invariants that must be preserved across fixes.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
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.