pre-mortem

pre-mortem is a skill for Claude Code, Codex from Ingramradical235/anty-framework. It costs 42 tokens per session (1,256 once invoked), scanned A, a copy of pre-mortem, MIT.

A planning exercise that imagines a strategy has completely failed and works backward to identify why. It pairs possible failures with prevention steps, backup plans, warning measures, and action thresholds.

In plain words
What is it for?
Use it before approving a strategy or major project, when a goal becomes uncertain, or when a team is relying on one optimistic plan. It helps rank failure scenarios and define when to switch approaches.
Why use it?
It reveals risks before a major initiative begins and gives the team a prepared response instead of forcing it to improvise after trouble appears.

Skill for Claude CodeCodex

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

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.

agentmods
npx agentmods add skills/ingramradical235/anty-framework/pre-mortem
Any agent
npx skills add Ingramradical235/anty-framework --skill pre-mortem
Clone the repo
git clone --depth 1 https://github.com/Ingramradical235/anty-framework

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/ingramradical235/anty-framework/pre-mortem.svg)](https://agentmods.dev/skills/ingramradical235/anty-framework/pre-mortem)
Your own site
<a href="https://agentmods.dev/skills/ingramradical235/anty-framework/pre-mortem"><img src="https://agentmods.dev/badge/skills/ingramradical235/anty-framework/pre-mortem.svg" alt="Measured on agentmods" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,256 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00042 $0.01256
Opus 5 $0.00021 $0.00628
Sonnet 5 $0.00008 $0.00251
Haiku 4.5 $0.00004 $0.00126

Measured 5d ago against content hash 56c48d2fbff5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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.

Origin

This is a copy

100% identical to pre-mortem — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

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

How it starts

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

Pre-Mortem & Scenario Planning

When to Apply

  • Before finalizing any Strategy Kernel
  • When planning a major initiative or Goal
  • When buffer enters YELLOW zone (validate contingencies)
  • When the founder is overly optimistic about a single plan
  • Quarterly strategy reviews

Core Framework

Pre-Mortem (5-Step Process)

  1. Assume total failure: "It is 6 months from now. This strategy has completely failed. Why?"
  2. Enumerate causes: List 3-5 specific, concrete failure scenarios (not vague risks)
  3. For each cause, define:
    • Prevention measure (what to do now)
    • Plan B (what to do if it happens)
    • Early warning KPI (what to watch)
    • Trigger threshold (when to act)
  4. Rank by likelihood x impact
  5. Embed triggers into the monitoring system so Plan B activates automatically
Failure cause: "LinkedIn organic saturated — ICP exhausted in target segment"
  Prevention: Track unique ICP accounts remaining; alert at <500
  Plan B: Pivot to content-first -> community -> warm intro strategy
  Early warning KPI: new connection acceptance rate declining
  Trigger: acceptance rate < 15% for 2 consecutive weeks

Scenario Planning (4 Scenarios with Auto-Triggers)

Define quantitative trigger points for each scenario. When thresholds are hit, Plan B activates AUTOMATICALLY — removing human judgment to prevent bias (loss aversion, sunk cost).

Scenario Condition Response
OPTIMISTIC Exceeds target by 20%+ Continue scaling. Increase targets.
BASE 80-120% of target Maintain strategy. Increase effort on constraint Driver.
PESSIMISTIC 40-80% of target + buffer RED + growth <3%/week for 3 weeks Auto-activate Plan B: pivot channel, reposition ICP, adjust pricing
CATASTROPHIC <40% of target + buffer >90% + negative growth for 2 weeks Full strategy reset: rebuild Strategy Kernel from scratch

Future State Narrative (PR/FAQ)

Before executing any major initiative, write success AS IF it already happened:

Read the full file on GitHub · 121 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. 5d ago First seen · 121 lines · 42 tokens per session scan A 56c48d2fbff5

Subscribe to this mod's changes

pre-mortem is a skill published in the GitHub repository Ingramradical235/anty-framework (1 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 1,256 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to pre-mortem, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

pipeline

Cash Machine 10-step B2B sales pipeline with 3 presets, verifiable checkpoints per step, trajectory logging, bottleneck detection with utilization formula, lead qualification gate (BANT 6-criteria), pipeline velocity and stall detection (2x threshold), two-tier probability scoring, BBS tracking, end-of-quarter…

VoxTechnologies/anty-framework · 84 tokens

quest-interview

QUEST Socratic interview methodology — beginner stance, empathic neutrality, downward/upward questioning, echo questions, concept identification, permission checks, critical point pursuit, anti-pattern safeguards, resolution imbalance diagnostic, workaround discovery, painkiller vs vitamin test, locally famous test.…

VoxTechnologies/anty-framework · 74 tokens

anticipatory-selling

Auto-generate 5 sales support materials for pipeline Steps 5-7 — competitive comparison table, 3-year TCO analysis, internal proposal template, objection rebuttals, phased implementation timeline. Core principle is arming the buyer to sell internally. Use when deals reach Step 5+ or when win rates at Steps 5-7 are low.

VoxTechnologies/anty-framework · 76 tokens

choice-architecture

Nudge-based choice architecture for 3-option selection UI — smart default vs active choice, outcome mapping, channel factors, RECAP, operational transparency with source attribution, post-decision reinforcement, error-forgiving undo, peak-end session design, user contribution acknowledgment. Use when presenting…

VoxTechnologies/anty-framework · 72 tokens

confidence

Contextual confidence calibration — DEFLATE for One-Way Doors and RED zones, PROTECT for Two-Way Doors and fundraising, "How does this work step by step?" depth testing, values-to-consequences redirect, unanimity as risk signal. From Knowledge Illusion — overconfidence is sometimes functional. Use when calibrating…

VoxTechnologies/anty-framework · 83 tokens

culture-map

Erin Meyer's Culture Map with 8 dimensions, 5 launch presets (US, JP, DE, UK, FR), Layer A agent-user adaptation, Layer B content-target market adaptation, and anti-sycophancy tone calibration per culture. Use when adapting communication style to the founder's culture, localizing content for target markets, or when…

VoxTechnologies/anty-framework · 79 tokens