design-pipeline: Skill for Claude Code

.agents/skills/bmad-sprint-status/SKILL.md

bmad-sprint-status is a skill for Claude Code, Codex from 2233admin/design-pipeline. It costs 20 tokens per session (555 once invoked), scanned A, original, MIT.

A deprecated status command that forwards requests to bmad-sprint-planning, the newer skill responsible for showing sprint status.

In plain words
What is it for?
Use it only when an existing workflow still refers to bmad-sprint-status; new sprint-status requests should use bmad-sprint-planning.
Why use it?
It preserves compatibility for older workflows and custom settings while directing new status requests to the replacement skill.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is 2233admin/design-pipeline's own configuration. It tells Claude Code and Codex how to work on design-pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything design-pipeline configures →

Reuse

Borrowing it

Nothing to install: this file belongs to 2233admin/design-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/2233admin/design-pipeline/main/.agents/skills/bmad-sprint-status/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/2233admin/design-pipeline

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.

agentmods badge for bmad-sprint-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-sprint-status/github.svg)](https://agentmods.dev/skills/2233admin/design-pipeline/bmad-sprint-status)
Your own site
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-sprint-status"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-sprint-status/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.

agentmods 80×15 button for bmad-sprint-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-sprint-status"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-sprint-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 555 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 original 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.1 $0.00020 $0.00555
Opus 5 $0.00010 $0.00278
Sonnet 5 $0.00004 $0.00111
Haiku 4.5 $0.00002 $0.00056

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

Security

Grade A, and why

bmad-sprint-status 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/bmad-sprint-status/SKILL.md · 27 lines

How it starts

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

DEPRECATED — forwards to bmad-sprint-planning (status view)

This skill was consolidated into bmad-sprint-planning, which now owns the whole sprint-status artifact: gate it, generate it, view it. It is retained as a thin compatibility shim so existing invocations by name and _bmad/custom/bmad-sprint-status.toml override files keep working. New work should invoke bmad-sprint-planning directly — "show sprint status" routes straight to the status view.

On Activation

  1. Resolve customization: uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. This picks up any {project-root}/_bmad/custom/bmad-sprint-status.toml and bmad-sprint-status.user.toml overrides for the legacy fields (activation_steps_prepend, activation_steps_append, persistent_facts, on_complete).

  2. Load {project-root}/_bmad/bmm/config.yaml (and config.user.yaml if present) to resolve {user_name} and {communication_language}.

  3. Emit a deprecation notice to the user in {communication_language}:

    Notice: bmad-sprint-status is deprecated and will be removed in a future release. It now forwards to bmad-sprint-planning, whose status view covers everything this skill did. To silence this notice, invoke bmad-sprint-planning directly next time (e.g. "show sprint status") and migrate any _bmad/custom/bmad-sprint-status.toml overrides to _bmad/custom/bmad-sprint-planning.toml.

  4. Invoke bmad-sprint-planning with the following context. Pass these as the activating context so it honors them instead of resolving its own customization from scratch:

    • Intent: status view — skip bmad-sprint-planning's usual intent detection and its readiness gate.
    • Pre-resolved legacy customization — use these in place of resolving from bmad-sprint-planning's own customize.toml for the four legacy fields: activation_steps_prepend, activation_steps_append, persistent_facts, and on_complete = the resolved values from step 1.
    • Original user input: forward whatever the user said when invoking this skill verbatim.

Read the full file on GitHub · 27 lines

Files

What ships with it

1 file 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.

  1. 10d ago First seen · 27 lines · 20 tokens per session scan A 95e695ce9665

Subscribe to this mod's changes

bmad-sprint-status is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 7d ago), licensed MIT. It adds 20 tokens to every session and 555 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

contribution-workflow

Create or document a contribution workflow for a design system — the multi-stage process for evaluating, accepting, and shepherding new contributions through to publication. Trigger when someone says: how should someone contribute, contribution process, adding a new component, contribution guidelines, what's the…

murphytrueman/design-system-ops · 99 tokens

backlog-generator

Transform audit findings into sprint-ready work items with effort estimates, acceptance criteria, and stakeholder-friendly rationale. This converts existing findings into tickets, NOT the process for contributing new components to the system. Trigger when someone says: generate backlog items, create tickets from…

murphytrueman/design-system-ops · 108 tokens

designlang-tokens

Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.

Manavarya09/design-extract · 30 tokens

omd-apply

A skill that applies a project's DESIGN.md file as visual and brand guidance for interface work. It covers components, colors, fonts, layout, copy, motion, and visual assets.

kwakseongjae/oh-my-design · 129 tokens

ss-review

Review UI code for design system compliance, accessibility, and best practices.

bitjaru/styleseed · 16 tokens

ss-reference

Compile screenshots, URLs, Figma exports, or an existing UI into a project-local StyleSeed output grammar with evidence, tokens, confidence, anti-patterns, and a validation screen. Use when the user supplies a design reference that StyleSeed does not already model.

bitjaru/styleseed · 56 tokens