pre-mortem

pre-mortem is a skill for Claude Code, Codex from fzfclee/consulting-skills. It costs 54 tokens per session (730 once invoked), scanned A, original, Apache-2.0.

A way to examine a plan by assuming it has already failed and then explaining the likely causes. The causes are turned into prevention actions and early warning signs.

In plain words
What is it for?
Use it to review a specific planned action, identify failure modes, define warnings, and assign prevention steps.
Why use it?
It reveals risks before a launch, project, deal, or change begins. This gives the team a chance to reduce preventable problems early.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to review a specific planned action, identify failure modes, define warnings, and assign prevention steps.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/fzfclee/consulting-skills/pre-mortem
Install

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.

Any agent
npx skills add fzfclee/consulting-skills --skill pre-mortem
Clone the repo
git clone --depth 1 https://github.com/fzfclee/consulting-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for pre-mortem

README.md
[![agentmods](https://agentmods.dev/badge/skills/fzfclee/consulting-skills/pre-mortem.svg)](https://agentmods.dev/skills/fzfclee/consulting-skills/pre-mortem)
Your own site
<a href="https://agentmods.dev/skills/fzfclee/consulting-skills/pre-mortem"><img src="https://agentmods.dev/badge/skills/fzfclee/consulting-skills/pre-mortem.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 730 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00730
Opus 5 $0.00027 $0.00365
Sonnet 5 $0.00011 $0.00146
Haiku 4.5 $0.00005 $0.00073

Measured 8d ago against content hash 9c0c8911dce4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

pre-mortem 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 8d 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.

skills/pre-mortem/SKILL.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pre Mortem

Use this skill to run Pre Mortem as a practical consulting method, not as a generic framework explanation.

Method Notes

  • Use prospective hindsight: assume the plan failed, then explain why.
  • Convert failure causes into prevention actions and early warnings.

Required Inputs

Collect or infer these inputs before execution:

  • planned action
  • success criteria
  • timeline
  • stakeholders
  • known risks

If an input is missing, do not block automatically. Mark it as missing, state the assumption used, and add a validation action.

When Not To Use

Do not use after a failure has already occurred; use root-cause analysis instead. A pre-mortem requires a specific plan and time horizon, not a generic list of things that might go wrong.

Adjacent Methods

  • risk-matrix: prioritize known risk events after they are identified.
  • scenario-planning: compare plausible external futures, not failure causes of one plan.

Step-by-Step Execution

Step Required input How to execute Output
Describe plan Plan, launch date, success criteria. State the plan as if the team believes it will work. Plan frame.
Assume failure Future date and failed outcome. Write a short future failure narrative. Failure scenario.
Generate causes Team concerns, dependencies, assumptions. List plausible reasons the plan failed. Failure cause list.
Prioritize preventable causes Cause list, likelihood, impact, controllability. Pick the causes worth preventing now. Priority failure modes.
Design prevention Priority causes. Define prevention actions, early warnings, owners, and contingencies. Pre-mortem action plan.

Output Template

### 1. Plan And Failure Horizon
Plan:
Launch / decision date:
Assumed failure date:
Success definition:

### 2. Failure Narrative
The plan failed because:
Observed consequences:
Earliest warning:

### 3. Failure Modes
| Failure mode | Cause | Preventability | Evidence | Priority |
|---|---|---|---|---|
|  |  |  |  |  |

### 4. Prevention Plan
| Prevention / contingency | Owner | Timing | Trigger |
|---|---|---|---|
|  |  |  |  |

### Evidence And Next Decision
- Confirmed facts:
- Assumptions:
- Missing evidence:
- Next action, owner, and timing:
- Expected signal and decision threshold:

Read the full file on GitHub · 87 lines

Changes

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.

  1. 8d ago First seen · 87 lines · 54 tokens per session scan A 9c0c8911dce4

Subscribe to this mod's changes

pre-mortem is a skill published in the GitHub repository fzfclee/consulting-skills (4 stars, last pushed 19d ago), licensed Apache-2.0. It adds 54 tokens to every session and 730 once invoked, about $0.0003 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-31.