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-entrygit 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-entry)<a href="https://agentmods.dev/skills/superplan-md/superplan-plugin/superplan-entry"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-entry/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-entry"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-entry.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.00038 | $0.05585 |
| Opus 5.5 | $0.00015 | $0.02234 |
| Sonnet 5.5 | $0.00008 | $0.01117 |
| Haiku 4.5 | $0.00004 | $0.00558 |
Grade A, and why
superplan-entry 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Superplan
Overview
Universal outer workflow layer for Superplan.
Internal category: workflow-control / execution-orchestration.
This skill replaces the entry discipline that using-superpowers used to provide.
Keep it small, but not permissive. Its job is to decide whether Superplan should meaningfully participate, whether readiness is missing, and which workflow phase owns the next responsibility.
If there is a meaningful chance that the request is repo work, use this skill before implementation, broad repo exploration, or clarifying questions.
Fast Trigger Rule
Treat this as an early trigger, not a late fallback.
- if there is even a modest chance the request is repo work, load this skill first
- do not wait for "proof" that the work is complex before routing
- do not keep the work inside
superplan-entryonce a narrower phase owner is clear
The value of this skill is early discrimination, not broad control.
Subagent Guard
If you were dispatched as a bounded subagent to execute, investigate, or verify a specific task, skip this skill.
Do not rerun top-level Superplan entry routing from inside a task-owned subagent unless the assignment explicitly says to reevaluate engagement.
Instruction Priority
Follow this order:
- direct user instructions and repo instructions such as
AGENTS.md,CLAUDE.md, or equivalent host guidance superplan-entryentry discipline- generic default behavior
If a repo instruction conflicts with a default Superplan habit, obey the user or repo instruction.
Mandatory Discipline
Treat entry routing as mandatory first-contact discipline, not optional advice.
- do not start implementing first and promise to structure later
- do not start broad repo exploration first and claim routing can happen after
- do not ask clarifying questions first when the real first question is whether Superplan should engage
- do not rationalize that a dense request is "probably just one task" without checking
- do not let "smallest useful depth" become a reason to skip an explicit route result
- do not begin execution for newly requested repo work until the route and shape chain is complete
What ships with it
10 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-fresh-request-active-task.md 928 B
- evals/02-interrupted-session-different-request.md 882 B
- evals/03-unrelated-dirty-worktree.md 979 B
- evals/README.md 3.8 KB
- references/entry-discipline.md 2.6 KB
- references/gotchas.md 1.1 KB
- references/memory-and-measurement.md 1.8 KB
- references/readiness.md 3.6 KB
- references/routing-boundaries.md 2.8 KB
- references/setup-config.md 1.8 KB
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 · 461 lines · 38 tokens per session scan A 879bbb152572
superplan-entry is a skill published in the GitHub repository superplan-md/superplan-plugin (75 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 5,585 once invoked, about $0.0002 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.