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 cuongtl1992/vibe-skills --skill bdd-practicesgit clone --depth 1 https://github.com/cuongtl1992/vibe-skillsWrote 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/cuongtl1992/vibe-skills/bdd-practices)<a href="https://agentmods.dev/skills/cuongtl1992/vibe-skills/bdd-practices"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/bdd-practices/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/cuongtl1992/vibe-skills/bdd-practices"><img src="https://agentmods.dev/badge/skills/cuongtl1992/vibe-skills/bdd-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00111 | $0.01067 |
| Opus 5 | $0.00056 | $0.00534 |
| Sonnet 5 | $0.00022 | $0.00213 |
| Haiku 4.5 | $0.00011 | $0.00107 |
Grade A, and why
bdd-practices 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cucumber BDD Best Practices
Guide teams through high-quality BDD practices across Discovery, Formulation, and Automation phases.
Three Core BDD Practices
1. Discovery — "What it could do"
Structured conversations to build shared understanding before coding.
- Example Mapping: Four-color index cards to map rules and examples
- OOPSI Mapping: Outcomes, Outputs, Processes, Scenarios, Inputs
- Feature Mapping: Identify actors, decompose tasks, map examples
Workshop setup: Three Amigos (PO + Dev + Tester), 25-30 min per User Story, as late as possible before development.
For detailed guidance, see references/discovery-workshop.md.
2. Formulation — "What it should do"
Structure examples into executable documentation using Gherkin.
Core principle: Treat readers the way you want to be treated — make it understandable to someone who doesn't know the feature.
Cardinal rule: One scenario, one behavior!
# ✅ DECLARATIVE — describes "what to do"
Scenario: Free subscribers can only see free articles
Given Free Frieda has a free subscription
When Free Frieda logs in with valid credentials
Then she sees a free article
# ❌ IMPERATIVE — describes "how to do it"
Scenario: Free subscribers can only see free articles
Given the user is on the login page
When I enter "[email protected]" in the Email field
And I click the "Submit" button
Then I see "FreeArticle1" on the homepage
Verification method: Ask "If the implementation changes, would this wording need to change?" If yes → rewrite.
For full Gherkin rules, step guidelines, and style standards, see references/gherkin-golden-rules.md.
3. Automation — "What it actually does"
Use automated examples to guide development: take one example → connect as test (fails) → implement (passes) → repeat.
Common Anti-Patterns
| Anti-Pattern | Signal | Fix |
|---|---|---|
| Procedure-driven tests | Multiple When-Then pairs | Split into separate scenarios |
| Overly imperative | UI details (click, field, button) | Describe behavior, not steps |
| Misused Scenario Outline | Equivalent class repetition | Only vary meaningful differences |
| Hardcoded test data | Brittle assertions on changing data | Pattern validation, hide data in step defs |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 117 lines · 111 tokens per session scan A dbf9a7d5c903
bdd-practices is a skill published in the GitHub repository cuongtl1992/vibe-skills (10 stars, last pushed 5mo ago), licensed MIT. It adds 111 tokens to every session and 1,067 once invoked, about $0.0006 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-31.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.