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-shapegit 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-shape)<a href="https://agentmods.dev/skills/superplan-md/superplan-plugin/superplan-shape"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-shape/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-shape"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-shape.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.00036 | $0.05017 |
| Opus 5.5 | $0.00014 | $0.02007 |
| Sonnet 5.5 | $0.00007 | $0.01003 |
| Haiku 4.5 | $0.00004 | $0.00502 |
Grade A, and why
superplan-shape 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 — 504 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shape Work
Overview
Create the minimum durable artifact structure and execution trajectory that preserves visibility, verification quality, and bounded execution.
This skill is not a task generator. It is a trajectory shaper.
Its job is to shape work so the agent can move with bounded autonomy while staying aligned to the user's real expectations. It must not collapse graph-shaped work into a single task merely because one agent could carry it alone.
Phase Ownership Rule
This skill owns artifact creation and execution trajectory, not open-ended analysis.
- shape the minimum durable structure that makes the next execution move safe
- choose the proof path before broad implementation starts
- once the executable frontier is clear, stop shaping and hand to execution
Trigger
Use when:
superplan-routehas decided Superplan should engage- the work needs durable structure created now
- the next step is to author plan, spec, or task artifacts proportional to the work
- the system must decide how much of the work is shapeable now versus discovery-driven
- the system must choose a verification loop before execution begins
Stay Out
Do not shape work when:
superplan-routedecided to stay out- execution is already fully shaped
- the request was already answered directly
- creating artifacts would add no value
Inputs And Assumptions
Inputs:
- routing decision and chosen depth
- user request and raw narrative when available
- repo state
- current
.superplan/artifacts if any - workspace context when available
- existing verification loops
- existing user-owned harnesses, scripts, custom skills, and workflows
- recent decision log entries when relevant
- known gotchas when relevant
Assumptions:
- depth determines how much structure to create
- not all work is fully deterministic at shaping time
- some work should be represented as investigation, prototype, or decision-gate work before deeper decomposition
- the right shaping output is often a trajectory, not a frozen perfect plan
- shaping should stop once the minimum useful artifact set and next executable frontier are clear
- multi-step work means work with 3 or more distinct steps, or work where sequencing across files or components matters; do not rationalize 3-step work as "only two steps" to skip graph shaping
- dense PRDs, JTBD dumps, implementation checklists, or multi-surface requests should default to multiple tracked tasks unless they truly collapse to one bounded executable unit
- if different parts of the work need different acceptance checks, they should usually not share one task contract
- when useful workspace or global skills already exist for planning, brainstorming, review, debugging, or verification, shaping should route execution toward them instead of inventing an ad hoc loop
What ships with it
7 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.
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 · 504 lines · 36 tokens per session scan A 803b75bf6c7c
superplan-shape is a skill published in the GitHub repository superplan-md/superplan-plugin (75 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 5,017 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.