postmortem-writer

postmortem-writer is a skill for Claude Code, Codex from aaronnat23/disp8ch. It costs 0 tokens per session (140 once invoked), scanned A, original, MIT.

A guide for writing calm, factual postmortems after incidents, outages, or serious mistakes. A postmortem records impact, timeline, causes, unknowns, and prevention work without blaming individuals.

In plain words
What is it for?
Use it to document incidents, separate root causes from contributing factors, and assign concrete prevention actions.
Why use it?
It turns a failure into a shared record of what happened and what should change, instead of relying on memory or blame.

Skill for Claude CodeCodex

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

Good fit Use it to document incidents, separate root causes from contributing factors, and assign concrete prevention actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aaronnat23/disp8ch/postmortem-writer
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 aaronnat23/disp8ch --skill postmortem-writer
Clone the repo
git clone --depth 1 https://github.com/aaronnat23/disp8ch

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 postmortem-writer

README.md
[![agentmods](https://agentmods.dev/badge/skills/aaronnat23/disp8ch/postmortem-writer/github.svg)](https://agentmods.dev/skills/aaronnat23/disp8ch/postmortem-writer)
Your own site
<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/postmortem-writer"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/postmortem-writer/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.

agentmods 80×15 button for postmortem-writer

Your own site · 80×15
<a href="https://agentmods.dev/skills/aaronnat23/disp8ch/postmortem-writer"><img src="https://agentmods.dev/badge/skills/aaronnat23/disp8ch/postmortem-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 140 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00000 $0.00140
Opus 5 $0.00000 $0.00070
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

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

Security

Grade A, and why

postmortem-writer 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 9d 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.

optional-skills/postmortem-writer/SKILL.md · 22 lines

What it actually says

Postmortem Writer

Write calm, factual incident reviews that improve the system instead of blaming people.

Use when

  • A production failure, outage, or serious mistake needs review.
  • You need an internal learning document after recovery.

Workflow

  1. Build a timeline from evidence, not memory.
  2. Separate impact, detection, response, root causes, and contributing factors.
  3. Avoid assigning personal blame; focus on system gaps and missing safeguards.
  4. Turn lessons into concrete prevention items with owners.
  5. State what remains unknown if the investigation is incomplete.

Deliverable

  • Impact summary.
  • Timeline.
  • Root causes.
  • Contributing factors.
  • Action items.
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. 9d ago First seen · 22 lines · 0 tokens per session scan A aece600ee7c2

Subscribe to this mod's changes

postmortem-writer is a skill published in the GitHub repository aaronnat23/disp8ch (100 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 140 tokens. 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-09-03.

Related

Other skills, from other repositories

agentlas-operations

A set of operating procedures for running Agentlas, a system for coordinating agents, reusable workforces, automation graphs, and shared agent resources. It covers candidate selection, graph creation, asset discovery, and memory rules.

agentlas-ai/Agentlas-OS · 67 tokens

todo-tracker

Persistent TODO scratch pad for tracking tasks across sessions. Use when the user asks to add, list, complete, remove, or summarize tasks in a portable workspace Markdown file. Uses stable task IDs and exact matching; heartbeat reporting is opt-in and count-only.

jdrhyne/agent-skills · 55 tokens

design-inventory

Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…

closedloop-ai/claude-plugins · 173 tokens

prd

A guide for writing a PRD, or Product Requirements Document, which explains what a product or feature should achieve and who it is for. It covers goals, users, success measures, limits, prior work, and excluded scope.

Insajin/autopus-adk · 11 tokens

cross-repo-cache

Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…

closedloop-ai/claude-plugins · 81 tokens

jira

Interact with Atlassian Jira from the terminal: search issues with JQL, view details, create issues, add comments, count matches with fast approximate-count, list projects, discover valid transitions, and change status. Includes a full JQL language reference (functions, operators, history predicates, date expressions…

magnus919/agent-skills · 144 tokens