write-bdd

write-bdd is a skill for Claude Code, Codex from RealManage/dx-training. It costs 15 tokens per session (527 once invoked), scanned A, original, no licence file.

A tool that turns plain-English requirements into Gherkin scenarios. Gherkin is a structured writing format often used for behaviour-driven development, where software behaviour is described as examples.

In plain words
What is it for?
Writing behaviour-driven development scenarios from feature requirements.
Why use it?
It gives requirements a consistent format that can be reviewed and used to define expected behaviour.

Skill for Claude CodeCodex

Part of the pm-toolkit plugin — 4 skills, 1 agent shipped together

Install

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.

agentmods
npx agentmods add skills/realmanage/dx-training/write-bdd
Any agent
npx skills add RealManage/dx-training --skill write-bdd
Clone the repo
git clone --depth 1 https://github.com/RealManage/dx-training

Made for: Claude Code, Codex.

Or install pm-toolkit, the plugin that ships this one along with the rest of its 4 skills, 1 agent.

Wrote 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.

agentmods badge for write-bdd

README.md
[![agentmods](https://agentmods.dev/badge/skills/realmanage/dx-training/write-bdd.svg)](https://agentmods.dev/skills/realmanage/dx-training/write-bdd)
Your own site
<a href="https://agentmods.dev/skills/realmanage/dx-training/write-bdd"><img src="https://agentmods.dev/badge/skills/realmanage/dx-training/write-bdd.svg" alt="Measured on agentmods" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 527 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00015 $0.00527
Opus 5 $0.00008 $0.00264
Sonnet 5 $0.00003 $0.00105
Haiku 4.5 $0.00002 $0.00053

Measured 4d ago against content hash 614b549299ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

write-bdd 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 4d 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.

courses/ai-101-claude-code/sessions/week-7/examples/pm-toolkit/skills/write-bdd/SKILL.md · 88 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 4d ago First seen · 88 lines · 15 tokens per session scan A 614b549299ee

Subscribe to this mod's changes

write-bdd is a skill published in the GitHub repository RealManage/dx-training (10 stars, last pushed 1mo ago), with no licence file. It adds 15 tokens to every session and 527 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

deck-course-module

暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.

nexu-io/html-anything · 25 tokens

ml-training-recipes

Battle-tested PyTorch training recipes for all domains — LLMs, vision, diffusion, medical imaging, protein/drug discovery, spatial omics, genomics. Covers training loops, optimizer selection (AdamW, Muon), LR scheduling, mixed precision, debugging, and systematic experimentation. Use when training or fine-tuning…

Orchestra-Research/AI-Research-SKILLs · 88 tokens

debug

Run /debug to find and fix a bug's root cause: a test failing for an unclear reason, /check verify finding a failure, or behavior being wrong. Runs a reproduce, localize, hypothesize, test, fix, verify loop, makes the minimal fix, and hands a regression test to /test. No features, no extra refactors.

jsmastery-pro/skills · 74 tokens

neohaskell-implementer

Write NeoHaskell (not vanilla Haskell) code in this repo — copy-adapt discipline, the fast repair loop, and the dialect escape hatch. Use when implementing or modifying any .hs file.

neohaskell/NeoHaskell · 48 tokens

neohaskell-security-design-review

Design-time security review of an approved contract-delta spec, before implementation. Runs when the spec's touches list intersects security-sensitive capabilities. Produces a LOCAL-only review record (gitignored, never pushed — a security review maps attack surface); enforced on the dev machine, not in CI.

neohaskell/NeoHaskell · 65 tokens

neo-cli-testing

Run and reason about the Neo CLI test layers under neo/ - unit, integration, e2e, and the generated-project / Neo-on-Neo smoke verification. Use before declaring any neo/ change done, or on "run the neo tests / cargo test / integration / e2e". Wraps the right command per layer inside nix develop, states network/Nix…

neohaskell/NeoHaskell · 105 tokens