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/christopherarter/superpowers-reasonix/superpowers-executing-plansnpx skills add christopherarter/superpowers-reasonix --skill superpowers-executing-plansgit clone --depth 1 https://github.com/christopherarter/superpowers-reasonixWrote 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/christopherarter/superpowers-reasonix/superpowers-executing-plans)<a href="https://agentmods.dev/skills/christopherarter/superpowers-reasonix/superpowers-executing-plans"><img src="https://agentmods.dev/badge/skills/christopherarter/superpowers-reasonix/superpowers-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.00026 | $0.00612 |
| Opus 5 | $0.00013 | $0.00306 |
| Sonnet 5 | $0.00005 | $0.00122 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
superpowers-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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Executing Plans
Overview
Load plan. Review critically. Execute all tasks. Report when complete.
Announce at start: "I'm using the superpowers-executing-plans skill to implement this plan."
Note: Reasonix has first-class subagent orchestration. Higher quality on multi-task plan: dispatch fresh subagent per task via native task tool (wait joins parallel jobs, review runs code-review) instead of inline. Use this skill when executing plan yourself, in-session, with checkpoints.
The Process
Step 1: Load and Review Plan
- Ensure an isolated workspace: use superpowers-using-git-worktrees to create one, or verify the existing one
read_filethe plan- Review critically — find questions or concerns
- Concerns? Raise with human partner before starting
- No concerns? Create
todo_writelist, proceed
Step 2: Execute Tasks
Per task:
- Mark in_progress
- Follow each step exactly (steps are bite-sized) — actually create the files the task specifies
- Run verifications as specified (via
bash) - Mark completed
Step 3: Complete Development
After all tasks complete and verified:
- Announce: "I'm using the superpowers-finishing-a-development-branch skill to complete this work."
- REQUIRED SUB-SKILL: use superpowers-finishing-a-development-branch skill
- Follow it: verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit blocker (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing start
- Don't understand an instruction
- Verification fails repeatedly
Ask for clarification. Never guess.
When to Revisit Earlier Steps
Return to Review (Step 1) when: partner updates plan from your feedback, or approach needs rethinking.
Don't force through blockers — stop and ask.
Remember
- Review plan critically first
- Follow plan steps exactly — actually create the files each task specifies
- Don't skip verifications. Run the tests the plan directs (use superpowers-verification-before-completion skill before claiming done)
- Reference skills when plan says to
- Report completion WITH evidence (test output) — never claim done blindly
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent
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 · 71 lines · 26 tokens per session scan A cb0c2fa3b39a
superpowers-executing-plans is a skill published in the GitHub repository christopherarter/superpowers-reasonix (96 stars, last pushed 15d ago), licensed MIT. It adds 26 tokens to every session and 612 once invoked, about $0.0001 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
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
gh-pr-review
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks…
prepare-release
Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.
claude-automation-recommender
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what…
gh-create-issue
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.
gh-create-pr
Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads .github/pullrequesttemplate.md, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of…