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/ao92265/claude-code-playbook/executing-plansnpx skills add ao92265/claude-code-playbook --skill executing-plansgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/executing-plans)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/executing-plans"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/executing-plans.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.00110 | $0.00621 |
| Opus 5 | $0.00055 | $0.00311 |
| Sonnet 5 | $0.00022 | $0.00124 |
| Haiku 4.5 | $0.00011 | $0.00062 |
Grade A, and why
executing-plans 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.
What it actually says
Executing Plans
Implement written plans through structured batches with review checkpoints.
When to Use
- A plan exists in
docs/plans/ - User says "execute the plan" or "implement the plan"
- After completing the writing-plans skill
- When resuming work on a documented plan
Process
Step 1: Load and Review
- Read the plan file from
docs/plans/ - Critically assess it - Does it still make sense?
- Raise concerns before proceeding
- Confirm understanding with user
Step 2: Execute Batch
Work through tasks in batches (typically 3 at a time):
- Mark progress - Note which task you're on
- Follow steps precisely - Don't skip verifications
- Run all commands - Check they produce expected output
- Commit after each logical unit
Step 3: Report Results
After each batch, use the batch report format from assets/execution-template.md.
Step 4: Continue or Adjust
Based on feedback:
- Continue - Execute next batch
- Adjust - Modify approach based on feedback
- Pause - Save progress and stop
Step 5: Complete Development
When all tasks done:
- Run final verification (all tests, linting)
- Summarize what was built
- Offer to commit/PR if not done
Critical Rules
STOP IMMEDIATELY When:
- Missing dependency - Something needed isn't available
- Unclear instructions - Plan step is ambiguous
- Failed verification - A check didn't pass
- Unexpected state - Reality doesn't match plan
Never force through obstacles or guess at solutions.
Return to Review When:
- Plan needs updating
- Fundamental approach needs to change
- New information changes requirements
Progress Tracking and Output Format
See assets/execution-template.md for the progress tracking block and per-task execution format.
Adapted from obra/superpowers executing-plans skill
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 · 93 lines · 110 tokens per session scan A 22ae4bf2160b
executing-plans is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 17d ago), licensed MIT. It adds 110 tokens to every session and 621 once invoked, about $0.0006 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
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
sap-transport-overview
System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system"…
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
pm-all
Skill "pm-all" from wei63w/pm-manager, covering user input, outline and shared workflow (all /pm- commands).
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
finn-spec
Interview the user about a raw idea until confident, then file a build-ready issue in Linear. Use when asked to run Finn-loop's spec interview, draft a queue-ready issue, or plan a feature. Interactive — requires the user present; never run unattended.