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-bdd-requirementsgit 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-bdd-requirements)<a href="https://agentmods.dev/skills/nwave-ai/nwave/nw-bdd-requirements"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-bdd-requirements/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-bdd-requirements"><img src="https://agentmods.dev/badge/skills/nwave-ai/nwave/nw-bdd-requirements.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.00031 | $0.02835 |
| Opus 5 | $0.00015 | $0.01418 |
| Sonnet 5 | $0.00006 | $0.00567 |
| Haiku 4.5 | $0.00003 | $0.00283 |
Grade A, and why
nw-bdd-requirements 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 10d 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BDD Requirements Discovery
"If you're not having conversations, you're not doing BDD." -- Liz Keogh
BDD discovers "what we don't know we don't know" through collaborative exploration with concrete examples, not tools or formats.
The Three Amigos
Three perspectives revealing each other's blindspots:
- Problem Owner (PO, BA, Domain Expert): business need | acceptance criteria | domain knowledge
- Problem Solver (Developer, Engineer): technical constraints | implementation complexity | technical edge cases
- Skeptic (Tester, QA): failure modes | edge cases and boundaries | challenge assumptions
Session Structure (25-minute timebox)
- Read user story aloud (2 min) -- shared context
- Identify acceptance criteria/rules (8 min) -- "what must be true for done?"
- Explore examples per rule (12 min) -- concrete scenarios, edge cases
- Capture questions (ongoing) -- unknowns on red cards
- Review and summarize (3 min) -- shared understanding check
If unmappable in 25 min: too large (split) | too uncertain (spike) | team needs practice.
Example Mapping
Four Card Types
- Yellow: User Story (1 per session) | Blue: Business Rules/AC | Green: Concrete Examples | Red: Questions/Unknowns (blockers)
Visual Layout
[Yellow] User Story: Transfer money between accounts
|
+-- [Blue] Rule: Amount must not exceed source balance
| +-- [Green] $500 balance, transfer $400 -> succeeds
| +-- [Green] $500 balance, transfer $500 -> succeeds (boundary)
| +-- [Green] $500 balance, transfer $501 -> fails
| +-- [Red] What happens if balance changes during transfer?
|
+-- [Blue] Rule: Both accounts belong to same customer
| +-- [Green] Transfer between checking and savings -> succeeds
| +-- [Green] Transfer to friend's account -> requires different flow
|
+-- [Blue] Rule: Transfer creates transaction records
+-- [Green] $100 transfer -> 2 transactions (debit + credit)
+-- [Red] What timezone for timestamps?
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.
- 10d ago First seen · 325 lines · 31 tokens per session scan A 6091f8a557c1
nw-bdd-requirements is a skill published in the GitHub repository nWave-ai/nWave (610 stars, last pushed 4d ago), licensed MIT. It adds 31 tokens to every session and 2,835 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-08-30.
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.
tdd-enforcement
Red-Green-Refactor TDD methodology with mandatory failing tests, minimal implementation, quality refactoring, and 80% coverage gating.
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.
story-development
Implement user stories with test-driven development methodology.
implement
Use when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify. Enforces TDD: a failing test comes before the code that makes it pass, one task at a time, appended to a progress ledger that survives compaction. Delegates test tooling…