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/execute-plannpx skills add danielvm-git/bigpowers --skill execute-plangit 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.00037 | $0.00587 |
| Opus 5 | $0.00018 | $0.00293 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
execute-plan 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Execute tasks from the active epic (specs/epics/eNN-slug/epic.yaml story tasks[]) one at a time, showing evidence after each step before proceeding.
HARD GATE — Do NOT proceed if on
mainormaster. Runkickoff-branchfirst.HARD GATE — Active epic must exist with runnable
verifyon each task. If missing, runplan-releasethenplan-workorbuild-epic.
Process
1. Read the plan
Read specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml. Parse depends-on in task descriptions for execution waves.
CONTEXT ISOLATION — Spawn each skill with a fresh context window. Pass decisions only through
specs/state.yamlhandoff— never rely on prior chat history.
Confirm with the user: step count, skip/reorder, stop-after step.
2. Execute step by step
For each task in the active story:
a. Announce — task desc and verify command.
b. Execute — code or delegate-task / dispatch-agents for waves.
c. Run verify — must be green before advancing.
d. Log — non-obvious decisions in specs/state.yaml under decisions[] or handoff block.
e. Checkpoint — ask to proceed unless autonomous mode requested.
f. Story UAT — after last task, run manual verification script from story notes or verify-work.
On verify failure: fix and re-run; never advance on red.
Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).
3. Blockers
Report blocker; ask skip/adapt/stop; update epic capsule if plan changes.
4. Final report
Suggest: verify-work → run-evals → audit-code → simulate-agents → commit-message → release-branch
Rules
- Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.
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 · 62 lines · 37 tokens per session scan A 553ec2a29e58
execute-plan is a skill published in the GitHub repository danielvm-git/bigpowers (156 stars, last pushed 25d ago), licensed MIT. It adds 37 tokens to every session and 587 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".