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-postmortemgit 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-postmortem)<a href="https://agentmods.dev/skills/superplan-md/superplan-plugin/superplan-postmortem"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-postmortem/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-postmortem"><img src="https://agentmods.dev/badge/skills/superplan-md/superplan-plugin/superplan-postmortem.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.00029 | $0.00341 |
| Opus 5.5 | $0.00012 | $0.00136 |
| Sonnet 5.5 | $0.00006 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
superplan-postmortem 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.
What it actually says
Retrospective Postmortem
Overview
Turn completed or failed work into reusable learning.
This skill exists to reduce repeated mistakes, not to assign blame.
Trigger
Use when:
- a task finished and the team wants to learn from it
- a task failed, thrashed, or took an unexpected path
- a recurring trap or process weakness became visible
Stay Out
Do not use when:
- execution is still actively blocked on basic facts
- the task is mid-flight and the right next move is still direct execution
- there is nothing durable to learn beyond ordinary completion notes
Core Rules
- separate facts, causes, and follow-up changes
- capture what went wrong and what almost went wrong
- identify one or two concrete rules, checks, or habits that would prevent recurrence
- keep the writeup concise enough to be reusable
- record recurring traps in
.superplan/gotchas.md - record process or policy changes in
.superplan/decisions.md
Forbidden Behavior
- blame-oriented writing
- vague lessons like "be more careful"
- rewriting history to make the path look cleaner than it was
- producing a long transcript instead of actionable learning
Handoff
Likely follow-ons:
superplan-guardwhen a test or proof path should be addedsuperplan-docswhen the docs or help misled the worksuperplan-shapewhen the underlying task breakdown needs to change
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 · 53 lines · 29 tokens per session scan A c76b7f5920c8
superplan-postmortem is a skill published in the GitHub repository superplan-md/superplan-plugin (75 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 341 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.