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 skills add superplan-md/superplan-plugin --skill superplan-executegit clone --depth 1 https://github.com/superplan-md/superplan-pluginWrote 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/superplan-md/superplan-plugin/superplan-execute)<a href="https://agentmods.dev/skills/superplan-md/superplan-plugin/superplan-execute"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-execute/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/superplan-md/superplan-plugin/superplan-execute"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-execute.svg" alt="Reviewed on agentmods" width="80" 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.00033 | $0.03781 |
| Opus 5.5 | $0.00013 | $0.01512 |
| Sonnet 5.5 | $0.00007 | $0.00756 |
| Haiku 4.5 | $0.00003 | $0.00378 |
Grade A, and why
superplan-execute 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 1mo 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 — 414 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Task Graph
Overview
Move graph-ready work forward without drifting into broad replanning or unnecessary CLI exploration.
This is the main execution control surface once work has been shaped. It should behave more like a scheduler and control plane than a single linear worker.
Execution should be primarily subagent-driven:
- select ready work
- dispatch bounded worker tasks
- dispatch verification in parallel where safe
- collect evidence and runtime signals
- decide continue, block, ask, review, or re-shape
Specific-Owner Rule
Once execution starts, prefer the narrowest execution sub-problem over broad workflow reconsideration.
- use
superplan-debugwhen a failure blocks forward motion - use
superplan-tddwhen a new behavior or bugfix can be expressed as a proof-first implementation step - use
superplan-verifywhen success claims are approaching faster than proof - use
superplan-reviewwhen the question becomes "is this task actually done?"
Trigger
Use when:
- there is executable tracked work
- at least one task is graph-ready
- the next need is to operate inside the shaped work rather than redesign it
- the system can make progress by dispatching one or more bounded work units
Stay Out
Do not run when:
- the system is still deciding whether Superplan should engage
- shaping has not happened yet
- context or bootstrap is the real missing prerequisite
- the graph is invalid enough that execution should stop and escalate
Inputs And Assumptions
Inputs:
- current task graph
- task contracts
- runtime state if present
- relevant workspace context
- current ready or blocking status
- relevant user-owned harnesses, scripts, custom skills, and workflows
- recent decision log entries affecting execution
- known workspace or task gotchas
Assumptions:
- execution should operate on ready work, not constantly redesign the project
- not every execution issue is a reason to reshape the graph
- multiple ready tasks may be best handled by subagents in parallel
- implementation and verification can sometimes run in parallel, but only when their contracts and write surfaces make that safe
- trajectory will change during execution; the key question is whether the change is local, structural, or strategic
- execution should route into existing workspace workflows rather than trying to replace them
- execution should stop reading and act once the next edit, command, or blocker transition is clear
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/01-priority-next-selection.md 686 B
- evals/02-graph-vs-runtime-blocked.md 749 B
- evals/03-review-ready-without-review-state.md 647 B
- evals/04-structural-drift-reshape.md 642 B
- evals/05-strategic-drift-reroute.md 633 B
- evals/06-runtime-fix-conflict.md 706 B
- evals/README.md 1.6 KB
- references/gotchas.md 1.2 KB
- references/lifecycle-semantics.md 2.3 KB
- references/runtime-state.md 2.7 KB
- references/subagent-dispatch.md 1.2 KB
- references/trajectory-changes.md 906 B
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.
- 1mo ago First seen · 414 lines · 33 tokens per session scan A 539fb0f2e023
superplan-execute is a skill published in the GitHub repository superplan-md/superplan-plugin (75 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 3,781 once invoked, about $0.0001 per session on Opus 5.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
cool-workflow
Use when the user asks for Cool Workflow, CW, agent workflow control-plane, TypeScript workflow orchestration, phased multi-agent work, background workflow tasks, reusable workflow apps, or auditable agent run state.
ci-triage
Diagnose failing CI, build, release-gate, or test runs for Cool Workflow. Use when a GitHub Actions check, local npm test, npm run build, release gate, smoke test, or generated-manifest check fails and Codex must identify the first actionable failure with logs and verifier commands.
deploy-check
Verify Cool Workflow release, publish, deploy, or package readiness. Use when Codex must check build/test gates, generated manifests, project index sync, dist/source contract, changelog/release notes, npm package contents, or pre-tag risk before shipping.
design-qa
Evaluate Cool Workflow architecture, product design, operator UX, context-pack, workflow-app, MCP/CLI, or release-process proposals. Use when Codex must decide whether a design respects FreeBSD/POLA, mechanism-not-policy, stable JSON surfaces, evidence, and verifier boundaries before implementation.
pr-review
Review Cool Workflow pull requests or branch diffs. Use when Codex must inspect code changes for bugs, regressions, FreeBSD/POLA violations, missing tests, generated artifact drift, release-contract risk, or CI implications, and return findings first with file/line citations.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.