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/boshu2/agentops/premortemnpx skills add boshu2/agentops --skill premortemgit clone --depth 1 https://github.com/boshu2/agentopsWrote 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/boshu2/agentops/premortem)<a href="https://agentmods.dev/skills/boshu2/agentops/premortem"><img src="https://agentmods.dev/badge/skills/boshu2/agentops/premortem.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.01669 |
| Opus 5 | $0.00019 | $0.00834 |
| Sonnet 5 | $0.00008 | $0.00334 |
| Haiku 4.5 | $0.00004 | $0.00167 |
Grade A, and why
premortem 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 3d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Premortem
Premortem is an optional plan-challenge strategy. It asks one fresh context to identify concrete ways the resolved bead or caller intent could fail before implementation. It is not part of the required RPI sequence and does not authorize readiness.
The first check: who verifies, and are they fresh?
Before any technical risk, test the plan's EVIDENCE SHAPE: for every unit of work, who verifies it, and is the verifying context distinct from the authoring context? A plan whose closure step is "the implementer runs its own tests and closes" contains no independent judgment anywhere — self-graded green is the classic false-done, and it outranks any single technical risk because it silently converts every other failure into a shipped one.
Measured 2026-08-04, probe
premortem-self-validation(gpt-5.6-luna, N=2, directional): without this doctrine loaded the producer named the planted self-validation flaw in 1/2 runs; with it loaded, 2/2. Ledger:evals/skill-probes/LEDGER.md. That row isLEGACY-UNVERIFIEDunder the current capture contract — replay cannot establish producer, configuration, or reproducibility — so treat this skill as unmeasured until a tier-2 probe under the current contract re-establishes it.
The second check: which steps are one-way doors?
After evidence shape, test the plan's REVERSIBILITY SHAPE. Walk the plan's steps and mark each one two-way (the plan can back out of it) or one-way (it cannot). For every one-way step, name three things: the exact undo cost, the point of no return, and who is holding the handle when it is crossed — the caller, or an agent auto-deciding inside a batch.
This ranks above every technical risk on a one-way step, because a two-way failure costs a retry and a one-way failure costs the thing itself. It also catches the plan shape that no single-step review sees: nineteen reversible steps followed by an irreversible one, where the reflex trained by the first nineteen answers the twentieth.
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.
- 3d ago First seen · 152 lines · 39 tokens per session scan A 9d1f527dbb41
premortem is a skill published in the GitHub repository boshu2/agentops (431 stars, last pushed 5d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,669 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
brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning, not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or…
doc-review
Use when the user asks to review or critique a prose planning document — a plan, spec, PRD, requirements doc, or design doc.
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
autolearn
Compound a solved problem into a durable in-repo learning doc. Use when a verified non-trivial fix lands, the user says "compound this", "document this fix", or "remember this". This is the automatic-capture entry point; for an explicitly requested one-off write-up, use compound.
doubt-driven
Doubt-driven adversarial review. Use when correctness matters more than speed, the code is unfamiliar, stakes are high, a claim can't be checked by the type system or compiler, or verifying now is cheaper than debugging later.
drift-detect
Use when the user says "plan drift", asks whether the roadmap, plans, or docs still match the code, or is deciding what to rebuild when restarting a stalled project. For doc-vs-code drift inside a specific diff, use sync-docs.