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/brunob54/superpowers-orchestrator/executing-plansnpx skills add brunob54/superpowers-orchestrator --skill executing-plansgit clone --depth 1 https://github.com/brunob54/superpowers-orchestratorWrote 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/brunob54/superpowers-orchestrator/executing-plans)<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>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.1 | $0.00060 | $0.00935 |
| Opus 5 | $0.00030 | $0.00467 |
| Sonnet 5 | $0.00012 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
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.
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
- Read the plan completely.
- Review critically — identify any questions or concerns.
- If concerns: raise them with the user before starting.
- 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:
- Follow each step exactly (plan has bite-sized steps with checkboxes).
- Run verifications as specified.
- Mark task complete.
- 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.
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.
- 5d ago First seen · 103 lines · 60 tokens per session scan A 24e1a78302c4
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.
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…
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…
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…
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.
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…
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.