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 commands/muhimu/claude-plan-lifecycle/execute-plangit clone --depth 1 https://github.com/muhimu/claude-plan-lifecycleWrote 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/commands/muhimu/claude-plan-lifecycle/execute-plan)<a href="https://agentmods.dev/commands/muhimu/claude-plan-lifecycle/execute-plan"><img src="https://agentmods.dev/badge/commands/muhimu/claude-plan-lifecycle/execute-plan.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 | $0.00084 | $0.05536 |
| Opus 5 | $0.00042 | $0.02768 |
| Sonnet 5 | $0.00017 | $0.01107 |
| Haiku 4.5 | $0.00008 | $0.00554 |
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 3d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Plan
Drive one plan from the plans dir end-to-end in the current worktree: invoke the chosen execution skill (superpowers:subagent-driven-development or superpowers:executing-plans) against it, verify (test/lint per the verify convention), commit and push, open a draft PR, and stamp the plan file with the PR number.
This command runs in a dedicated git worktree (created by your worktree manager of choice or plain git worktree add). It refuses to run in the main checkout.
Step 1 — Pre-flight checks
Run each check in order. On any failure, stop: print the message and end the turn.
-
Inside a git worktree?
git rev-parse --is-inside-work-treeIf not, stop: "Not inside a git working tree."
-
Worktree, not main checkout?
git rev-parse --git-dirIf output is
.git(or an absolute path ending in/.git), this is the main checkout, not a worktree. Stop: "This command refuses to run in the main checkout. Create a worktree (git worktree addor your worktree manager) and run it there."If output contains
.git/worktrees/<name>, you're in a worktree. Continue. -
Branch is not the default branch? Resolve the repo's default branch once — every later mention of
$DEFAULT_BRANCHin this command means this value:DEFAULT_BRANCH="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')" [ -n "$DEFAULT_BRANCH" ] || DEFAULT_BRANCH="$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name)" git rev-parse --abbrev-ref HEADIf the current branch is
$DEFAULT_BRANCH(ormain/master), stop: "Worktree is on a protected branch. Switch to a feature branch first." -
Tree state:
git status --porcelainIf non-empty, warn ("Worktree has uncommitted changes —
executing-planswill likely commit them as part of execution") but continue. -
Execution skills available? This command drives plans via the superpowers plugin. If neither
superpowers:executing-plansnorsuperpowers:subagent-driven-developmentappears in the available-skills list, stop: "The superpowers plugin is required (https://github.com/obra/superpowers). Install it and re-run."
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.
- 3d ago First seen · 374 lines · 84 tokens per session scan A 286061a26841
execute-plan is a command published in the GitHub repository muhimu/claude-plan-lifecycle (2 stars, last pushed 7d ago), licensed MIT. It adds 84 tokens to every session and 5,536 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.