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/plan-releasenpx skills add danielvm-git/bigpowers --skill plan-releasegit 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.00072 | $0.01679 |
| Opus 5 | $0.00036 | $0.00839 |
| Sonnet 5 | $0.00014 | $0.00336 |
| Haiku 4.5 | $0.00007 | $0.00168 |
Grade A, and why
plan-release 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Release
HARD GATE — Do NOT run this skill unless
elaborate-spechas produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, runelaborate-specfirst. HARD GATE —specs/product/SCOPE_LATEST.yaml(or legacyspecs/product/SCOPE_LATEST.yaml) must exist. If missing, runscope-workfirst.
Synthesize the conversation context into specs/release-plan.yaml (index) and shard detail under specs/epics/. No new interview — only clarify if something is genuinely ambiguous.
Outputs
| File | Content |
|---|---|
specs/release-plan.yaml |
release.version, semver bump hint, WSJF-ordered epic list with id, capsule_dir, wsjf, bcps — no story status |
specs/epics/eNN-<slug>/epic.yaml |
Epic manifest: id, title, wsjf, total_bcps, status, stories[] list |
specs/epics/eNN-<slug>/eNNsYY-<slug>.md |
Story spec in countable-story-format.md with 20 sections and Gherkin acceptance criteria |
specs/epics/eNN-<slug>/eNNsYY-tasks.yaml |
Decoupled task checklist with verify: commands per task |
specs/execution-status.yaml |
Flat key-value store for story status (eNNsYY: todo) |
Epic Capsule Structure
All epics use capsule directories (no flat/folder distinction):
specs/epics/e01-auth-system/
├── epic.yaml # Epic manifest
├── adr/ # Epic-local ADRs (created lazily)
├── e01s01-login.md # Story spec (countable-story-format)
├── e01s01-tasks.yaml # Decoupled task checklist
├── e01s02-jwt.md # Story spec
└── e01s02-tasks.yaml # Decoupled task checklist
Rationale: Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec .md from execution -tasks.yaml (C1).
Process
1. Draft epics and stories
From the conversation context, define:
- Epics —
e01,e02, … (stable IDs; WSJF order inrelease-plan.yamlonly) - Stories —
e01s01,e01s02, … with Gherkin acceptance criteria
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 · 146 lines · 72 tokens per session scan A e02630810cf7
plan-release is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 72 tokens to every session and 1,679 once invoked, about $0.0004 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".