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/superplan-md/superplan-plugin/superplan-releasenpx skills add superplan-md/superplan-plugin --skill superplan-releasegit clone --depth 1 https://github.com/superplan-md/superplan-pluginWhat 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.00033 | $0.00288 |
| Opus 5 | $0.00016 | $0.00144 |
| Sonnet 5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
superplan-release 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 2d 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.
What it actually says
Release Readiness
Overview
Decide whether the current product slice is honestly ready to ship.
Trigger
Use when:
- the user asks "is this prod ready?"
- a release, publish, or rollout decision is being made
- the repo needs one last quality gate before recommending adoption
Core Rules
- run the strongest relevant verification path first
- prefer full-suite or release-equivalent checks when they exist
- include install, update, docs, and help-surface sanity checks when they affect real users
- distinguish "ready for this scope" from "ready for every future direction"
- name blockers plainly when the answer is no
Minimal Checklist
- build and test status
- runtime and doctor health
- install and update story
- user-facing docs/help alignment
- known high-risk gaps or unresolved failures
Forbidden Behavior
- calling something production-ready on partial proof
- hiding failures because they seem small
- widening the claimed scope beyond what was actually verified
Handoff
Likely follow-ons:
superplan-verifyfor missing proofsuperplan-docsfor stale release docssuperplan-executefor the concrete blocker fixes
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.
- 2d ago First seen · 49 lines · 33 tokens per session scan A 8f4b320f8ed1
superplan-release is a skill published in the GitHub repository superplan-md/superplan-plugin (72 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 288 once invoked, about $0.0002 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
evolve
Research-driven multi-cycle improvement director. Forms causal hypotheses about why scores are low, validates them with scout agents before attacking, dispatches axis-parallel fleet attacks, extracts transferable patterns, and runs indefinitely within a budget envelope. Accumulates a persistent belief model and…
improve
Autonomous quality improvement loop. Scores a target against a rubric, selects the highest-leverage axis, attacks it, verifies, documents, and loops. No pre-planning between iterations — each loop re-scores from scratch.
setup
First-run experience for the harness. Three modes: Recommended (guided, 3 min), Full Tour (guided + skill walkthrough, 8 min), and Express (zero questions, 30 sec). Installs hooks first, detects stack, configures harness.json, runs a live demo on real code, and prints a reference card.
ascii-diagram
Generate perfectly aligned ASCII diagrams — architecture, flow, sequence, box-and-arrow. Uses a programmatic character-grid approach so alignment is guaranteed by math, not token prediction. Includes post-render verification.
research
Focused research investigations. Converts questions into structured findings with confidence levels and source citations. Single agent by default; with --parallel (or when the question decomposes into 3+ independent angles) it spawns scout agents whose findings are compressed into a unified brief. Does not make…
triage
GitHub issue and PR investigator. Pulls open issues/PRs, classifies them, searches the codebase for root cause or reviews contributed code, proposes fixes with file:line references, and optionally implements fixes. Use for investigating GitHub issues and reviewing PRs; do NOT use for general code review unrelated to…