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 marlonvidal/tech-manager-os --skill bmad-v6-story-pipelinegit clone --depth 1 https://github.com/marlonvidal/tech-manager-osWrote 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/marlonvidal/tech-manager-os/bmad-v6-story-pipeline)<a href="https://agentmods.dev/skills/marlonvidal/tech-manager-os/bmad-v6-story-pipeline"><img src="https://agentmods.dev/badge/skills/marlonvidal/tech-manager-os/bmad-v6-story-pipeline/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/marlonvidal/tech-manager-os/bmad-v6-story-pipeline"><img src="https://agentmods.dev/badge/skills/marlonvidal/tech-manager-os/bmad-v6-story-pipeline.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.00060 | $0.01612 |
| Opus 5 | $0.00030 | $0.00806 |
| Sonnet 5 | $0.00012 | $0.00322 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
bmad-v6-story-pipeline 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 12d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BMAD Story Pipeline Orchestrator
Run the complete story lifecycle — from backlog to done — in one command by dispatching a fresh subagent for each stage. Automatically detects story status and skips stages that are already complete.
Pipeline Stages
| # | Stage | Skill invoked | Produces | Status transition |
|---|---|---|---|---|
| 1 | Create Story | bmad-create-story |
{impl}/{{story_key}}.md |
backlog → ready-for-dev |
| 2 | Dev Story | bmad-dev-story |
implemented code, tests green | ready-for-dev → review |
| 3 | Code Review | bmad-code-review |
review findings, auto-fix | review → done (or in-progress) |
Initialization
1. Load configuration
Read {project-root}/_bmad/bmm/config.yaml and resolve:
project_name,user_namecommunication_language,document_output_languageimplementation_artifacts(abbrev{impl})output_folderplanning_artifacts
2. Discover next story
Read the FULL {impl}/sprint-status.yaml.
If the user provided a specific story key: use that key directly. Look up its current status in development_status. This lets a team member explicitly pick a story even if another story has higher priority by status.
If no story key provided: auto-discover using priority-based search. Scan development_status entries top-to-bottom (only keys matching pattern N-N-slug, not epic-N or *-retrospective) in this priority order:
- First story with status
in-progress(resume interrupted work) - If none, first story with status
review - If none, first story with status
ready-for-dev - If none, first story with status
backlog
If no story found in any of those statuses, report to the user that all stories are complete (or no stories exist) and HALT.
Extract from the selected story:
story_key— the full key (e.g.1-2-integrate-earnings-dashboard)story_id—{epic_num}-{story_num}(e.g.1-2)epic_key—epic-{epic_num}story_status— the current status value
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.
- 12d ago First seen · 154 lines · 60 tokens per session scan A 45aa4c04f6b3
bmad-v6-story-pipeline is a skill published in the GitHub repository marlonvidal/tech-manager-os (17 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,612 once invoked, about $0.0003 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…