executing-plans

executing-plans is a skill for Claude Code, Codex from brunob54/superpowers-orchestrator. It costs 60 tokens per session (935 once invoked), scanned A, original, MIT.

A procedure for implementing an existing plan in controlled batches with checks after each batch.

In plain words
What is it for?
It helps load and review a plan, implement its tasks, run verification, and then hand the completed branch to the branch-finishing procedure.
Why use it?
It prevents a long planned change from proceeding unchecked and stops to resolve concerns or verification failures.

Skill for Claude CodeCodex

Part of the superpowers-orchestrator plugin — 28 skills, 2 agents, 6 hooks shipped together

Install

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.

agentmods
npx agentmods add skills/brunob54/superpowers-orchestrator/executing-plans
Any agent
npx skills add brunob54/superpowers-orchestrator --skill executing-plans
Clone the repo
git clone --depth 1 https://github.com/brunob54/superpowers-orchestrator

Made for: Claude Code, Codex.

Or install superpowers-orchestrator, the plugin that ships this one along with the rest of its 28 skills, 2 agents, 6 hooks.

Wrote 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.

agentmods badge for executing-plans

README.md
[![agentmods](https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/executing-plans.svg)](https://agentmods.dev/skills/brunob54/superpowers-orchestrator/executing-plans)
Your own site
<a href="https://agentmods.dev/skills/brunob54/superpowers-orchestrator/executing-plans"><img src="https://agentmods.dev/badge/skills/brunob54/superpowers-orchestrator/executing-plans.svg" alt="Measured on agentmods" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 935 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.00935
Opus 5 $0.00030 $0.00467
Sonnet 5 $0.00012 $0.00187
Haiku 4.5 $0.00006 $0.00093

Measured 5d ago against content hash 24e1a78302c4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

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 5d 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.

skills/executing-plans/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Executing Plans

Implement an approved plan in controlled batches with explicit verification.

Required Start

Announce: I'm using the executing-plans skill to implement this plan.

Process

digraph executing_plans {
    "Load and review plan" [shape=box];
    "Concerns?" [shape=diamond];
    "Raise with user" [shape=box];
    "Set up worktree" [shape=box];
    "Execute next task" [shape=box];
    "Run verification" [shape=box];
    "More tasks?" [shape=diamond];
    "Invoke finishing-a-development-branch" [shape=doublecircle];

    "Load and review plan" -> "Concerns?";
    "Concerns?" -> "Raise with user" [label="yes"];
    "Raise with user" -> "Load and review plan" [label="plan updated"];
    "Concerns?" -> "Set up worktree" [label="no"];
    "Set up worktree" -> "Execute next task";
    "Execute next task" -> "Run verification";
    "Run verification" -> "More tasks?";
    "More tasks?" -> "Execute next task" [label="yes"];
    "More tasks?" -> "Invoke finishing-a-development-branch" [label="no"];
}

Step 1: Load and Review Plan

  1. Read the plan completely.
  2. Review critically — identify any questions or concerns.
  3. If concerns: raise them with the user before starting.
  4. If no concerns: create task tracking and proceed.

Step 2: Set Up Workspace

If working on main/master branch AND the plan involves code changes:

  • Set up isolated workspace via using-git-worktrees.

If already on a feature branch, or the plan is documentation/config only:

  • Skip worktree setup. Confirm with user that the current branch is appropriate.

Step 3: Execute Tasks

For each task:

  1. Follow each step exactly (plan has bite-sized steps with checkboxes).
  2. Run verifications as specified.
  3. Mark task complete.
  4. For tasks involving UI/UX or frontend implementation, apply guidance from frontend-design.

Note: Superpowers works significantly better with subagent support. If subagents are available, use subagent-driven-development instead — the quality of work will be higher with fresh-context-per-task and two-stage review gates.

Read the full file on GitHub · 103 lines

Changes

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.

  1. 5d ago First seen · 103 lines · 60 tokens per session scan A 24e1a78302c4

Subscribe to this mod's changes

executing-plans is a skill published in the GitHub repository brunob54/superpowers-orchestrator (3 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 935 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

github-pr-review

Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…

fvadicamo/dev-agent-skills · 95 tokens

decision-records

Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks…

fvadicamo/dev-agent-skills · 113 tokens

privacy-guard

Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…

fvadicamo/dev-agent-skills · 128 tokens

github-pr-merge

Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.

fvadicamo/dev-agent-skills · 72 tokens

github-pr-creation

Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…

fvadicamo/dev-agent-skills · 75 tokens

git-commit

Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.

fvadicamo/dev-agent-skills · 49 tokens