What is bmad-dev-story?

A development workflow that implements a prepared story specification. It follows the story's tasks and acceptance criteria, which are the conditions used to decide whether the work is complete.

Use it to implement a named story or the next story in a sprint plan. It handles the specified coding tasks, checks the acceptance criteria, and records completion details.

It gives the developer agent the context needed to implement the intended change and keeps the story record updated with progress, files, and results.

bmad-dev-story — Skill for Claude Code and Codex by mmornati

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.

Any agent

npx skills add mmornati/leanproxy-mcp --skill bmad-dev-story

Clone the repo

git clone --depth 1 https://github.com/mmornati/leanproxy-mcp

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-dev-story/github.svg)](https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-dev-story)

Your own site

<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-dev-story"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-dev-story/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mmornati/leanproxy-mcp/bmad-dev-story"><img src="https://agentmods.dev/badge/skills/mmornati/leanproxy-mcp/bmad-dev-story.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,948 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5.1	$0.00040	$0.05948
Opus 5	$0.00020	$0.02974
Sonnet 5	$0.00008	$0.01190
Haiku 4.5	$0.00004	$0.00595

Measured 9d ago against content hash f12801307b15, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bmad-dev-story 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 9d 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.

Origin

This is a copy

92% identical to bmad-dev-story — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/bmad-dev-story/SKILL.md · 501 lines

How it starts

The opening of the file, as written. The whole thing — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dev Story Workflow

Goal: Execute story implementation following a context filled story spec file.

Your Role: Developer implementing the story.

Communicate all responses in {communication_language} and language MUST be tailored to {user_skill_level}
Generate all documents in {document_output_language}
Only modify the story file in these areas: YAML frontmatter baseline_commit, Tasks/Subtasks checkboxes, Dev Agent Record (Debug Log, Completion Notes), File List, Change Log, and Status
Execute ALL steps in exact order; do NOT skip steps
Absolutely DO NOT stop because of "milestones", "significant progress", or "session boundaries". Continue in a single execution until the story is COMPLETE (all ACs satisfied and all tasks/subtasks checked) UNLESS a HALT condition is triggered or the USER gives other instruction.
Do NOT schedule a "next session" or request review pauses unless a HALT condition applies. Only Step 9 decides completion.
User skill level ({user_skill_level}) affects conversation style ONLY, not code updates.

Conventions

Bare paths (e.g. steps/step-01-init.md) resolve from the skill root.
{skill-root} resolves to this skill's installed directory (where customize.toml lives).
{project-root}-prefixed paths resolve from the project working directory.
{skill-name} resolves to the skill directory's basename.

On Activation

Step 1: Resolve the Workflow Block

Run: python3 {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow

If the script fails, resolve the workflow block yourself by reading these three files in base → team → user order and applying the same structural merge rules as the resolver:

{skill-root}/customize.toml — defaults
{project-root}/_bmad/custom/{skill-name}.toml — team overrides
{project-root}/_bmad/custom/{skill-name}.user.toml — personal overrides

Any missing file is skipped. Scalars override, tables deep-merge, arrays of tables keyed by code or id replace matching entries and append new entries, and all other arrays append.

Read the full file on GitHub · 501 lines

Files

What ships with it

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

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.

9d ago First seen · 501 lines · 40 tokens per session scan A f12801307b15

Subscribe to this mod's changes

bmad-dev-story is a skill published in the GitHub repository mmornati/leanproxy-mcp (5 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 5,948 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to bmad-dev-story, differing in 31 lines, and is treated as a copy.

Planning Project management developer-tools go mcp open-source proxy

bv

Beads Viewer - Graph-aware triage engine for Beads projects. Computes PageRank, betweenness, critical path, and cycles. Use --robot- flags for AI agents.

Dicklesworthstone/beads_viewer · 39 tokens

mx-flow

Full development workflow orchestrator: brainstorm → plan → worktree → convergent TDD/review loop → verify → PR. One human gate (spec approval); all other gates auto-proceed. Use when starting a feature or significant change from scratch. Usage: /mx-flow ; /mx-flow status [name]; /mx-flow finish .

maxence2997/mx-harness · 75 tokens

bmad-dev-story