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 agentmods add skills/danielvm-git/bigpowers/compose-workflownpx skills add danielvm-git/bigpowers --skill compose-workflowgit clone --depth 1 https://github.com/danielvm-git/bigpowersWhat 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 | $0.00042 | $0.00803 |
| Opus 5 | $0.00021 | $0.00402 |
| Sonnet 5 | $0.00008 | $0.00161 |
| Haiku 4.5 | $0.00004 | $0.00080 |
Grade A, and why
compose-workflow 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 2d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story: e09s01
story: e45s27
story: e21s04
Compose Workflow
HARD GATE — HARD GATE — Workflows are orchestration, not automation. Do NOT create workflows for tasks that should be single skills. Workflow complexity must be justified.
Process
- Interview: goal, phases, which skills, gates between steps.
- Write
specs/workflows/<name>.yaml:name,command,description,skills[],verify- Optional:
argsfor skill-specific arguments
- Register in state.yaml Active Decisions.
- Optional: reference from
orchestrate-projectAd-Hoc mode.
Prefer the YAML recipe format over the legacy
specs/WORKFLOW-<name>.mdmarkdown format. YAML recipes are command-mappable, machine-readable, and listed in the Standard Recipe Library.
Terminal-state taxonomy (e45s27)
Every workflow step and /loop tick MUST exit with exactly one terminal state:
| State | Meaning | Next action |
|---|---|---|
success |
Step verify passed; artifacts written | Advance to next skill in recipe |
no-op |
Nothing to do (already green / already applied) | Skip step; advance |
blocked |
External gate (approval, red CI, missing dep) | diagnose-stall or escalate to user |
exhausted |
Max iterations/cycles reached (review cap, dispatch cycles) | Stop; human decision required |
Record terminal state in specs/state.yaml handoff.last_terminal_state when a recipe step completes. /loop ticks that produce no progress for two consecutive wakes → invoke diagnose-stall.
Standard Recipe Library
Pre-built recipes in specs/workflows/ map agentic stack commands to skill chains.
Reference them in AGENTS.md so /command directly invokes the matching recipe.
| Command | Workflow | Skill chain |
|---|---|---|
/check-stack |
check-stack | survey-context → assess-impact → setup-environment |
/ship |
ship | audit-code → commit-message → release-branch |
/tdd |
tdd | develop-tdd → enforce-first |
/code-review |
code-review | audit-code → request-review → respond-review |
/security |
security | audit-code → request-review |
/plan |
plan | survey-context → research-first → plan-work |
/build-fix |
build-fix | investigate-bug → diagnose-root → develop-tdd → validate-fix |
/e2e |
e2e | smoke-test → verify-work |
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.
- 2d ago First seen · 83 lines · 42 tokens per session scan A 82ffbbd98052
compose-workflow is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 42 tokens to every session and 803 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-30.
Other skills, from other repositories
shared/tech-stack-detection
检测项目技术栈的通用方法，通过分析配置文件识别语言、框架、工具链.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
boss
可审计的 agent 团队：BMAD 全自动研发流水线编排器。编排 9 个专业 Agent（PM、架构师、UI Designer、Tech Lead、Scrum Master、Frontend、Backend、QA、DevOps）从需求到部署，每一步都有事件溯源 + 不可绕过门禁 + 确定性 eval——可验证测试真跑、门禁真过。支持单环节切片命令（/boss:plan /review /qa /ship）与无 CLI 纯 Markdown 降级。 Triggers: 'boss mode', '/boss', '全自动开发', '从需求到部署', '帮我做一个', 'build this', 'ship it', '全流程'…
debloat
Compress an artifact that has accreted into bloat — padding, over-qualification, fused sentences, walls of enumeration, adjacent restatement — down to its load-bearing density, meaning preserved. Use when prose is correct and current but has grown verbose or patched-over and you want it tight without a full rewrite.
bmad-dev-story
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan".
bmad-validate-prd
Validate a PRD against standards. Use when the user says "validate this PRD" or "run PRD validation".