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.
curl -O https://raw.githubusercontent.com/2233admin/design-pipeline/main/.agents/skills/bmad-project-context/SKILL.mdgit clone --depth 1 https://github.com/2233admin/design-pipelineWrote 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/2233admin/design-pipeline/bmad-project-context)<a href="https://agentmods.dev/skills/2233admin/design-pipeline/bmad-project-context"><img src="https://agentmods.dev/badge/skills/2233admin/design-pipeline/bmad-project-context.svg" alt="Measured on agentmods" 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.00049 | $0.01853 |
| Opus 5 | $0.00024 | $0.00927 |
| Sonnet 5 | $0.00010 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
bmad-project-context 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bmad-project-context — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
A conversation that produces a repository's agent instructions: a small verified block inside AGENTS.md. The user brings rules they want followed — governance, security, standards — and the repository supplies the rest, verified.
Conversational always; the user approves every write.
Args: intent (setup | refresh | record | audit); a target repo or path; extra source paths or URLs. Supplied values skip their questions.
Resolution rules
- Bare paths and
{skill-root}(e.g.references/best-practices.md) resolve from this skill's installed directory. {project-root}→ the project working directory.- Target → the repository being described, defaulting to
{project-root}. If it resolves to more than one working tree, or to one the user cannot commit in, ask before writing.
On Activation
- Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --key workflow. On failure, read{skill-root}/customize.tomldirectly and use defaults. Execute{workflow.activation_steps_prepend}; treat{workflow.persistent_facts}entries as standing context (file:= paths/globs to load, others verbatim). - Config: if
{project-root}/_bmadexists,uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}and read{user_name},{communication_language}(use it every turn),{output_folder}. Standalone: skip. - Load
references/best-practices.mdandreferences/template.mdbefore anything else. Every decision below is made against them. - Detect intent and greet
{user_name}: setup (no block in the target — the default), refresh (a block exists), record (the user reports a mistake agents made), audit (re-verify and prune). Fold{workflow.external_sources}into the source list. Execute{workflow.activation_steps_append}.
Setup and Refresh Steps
No writes until step 5!
1. Assess and report
Read AGENTS.md, harness or agent specific rule files, docs folders, and any notes carrying lessons. Report what exists and how it measures up, per best-practices.md.
What ships with it
3 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.
- 7d ago First seen · 111 lines · 49 tokens per session scan A 1a276f306ed7
bmad-project-context is a skill published in the GitHub repository 2233admin/design-pipeline (9 stars, last pushed 4d ago), licensed MIT. It adds 49 tokens to every session and 1,853 once invoked, about $0.0002 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
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.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
ss-pattern
Generate a composed UI pattern from the active StyleSeed grammar and brand recipe using existing primitives.
ss-restyle
Apply one optional StyleSeed aesthetic profile without changing the selected output grammar, product job, or core design judgment.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
governance-encoder
Convert governance policies into machine-executable JSON constraint files that AI agents and CI pipelines validate against automatically. This produces rule engine files in .ai/governance/, NOT narrative decision records or documentation. Trigger when someone says: encode governance rules, governance as code, automate…