agentmods.dev

postmortem

postmortem is a skill for Claude Code from MotWakorb/ai-agent-dev-team. It costs 48 tokens per session (2,961 once invoked), scanned A, original, MIT.

A blameless report about a service failure or other incident, explaining what happened, why it happened, and how to prevent it happening again.

In plain words
What is it for?
Use it to build an evidence-based timeline, analyze contributing factors, and define preventive actions after an incident.
Why use it?
It focuses on weaknesses in systems and processes instead of blaming individuals, while keeping follow-up work suited to the affected system's deployment level.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths.

not rated 2repo 2mo ago A scan 48 tokens original MIT

Good fit Use it to build an evidence-based timeline, analyze contributing factors, and define preventive actions after an incident.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/motwakorb/ai-agent-dev-team/postmortem
View source ↗ MotWakorb/ai-agent-dev-team
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 MotWakorb/ai-agent-dev-team --skill postmortem
Clone the repo
git clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-team

Made for: Claude Code.

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

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

agentmods 80×15 button for postmortem

Your own site · 80×15
<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/postmortem"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/postmortem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,961 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.00048 $0.02961
Opus 5.5 $0.00019 $0.01184
Sonnet 5.5 $0.00010 $0.00592
Haiku 4.5 $0.00005 $0.00296

Measured 2mo ago against content hash d56fe8cede61, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 2mo 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.

postmortem/SKILL.md · 265 lines

How it starts

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

Incident Postmortem

Blameless. The question is "what failed?" not "who failed?" If a human error caused the incident, the system that allowed the human error is the root cause. We fix systems, not blame people.

Preflight: Verify Onboarding & Effective Tier

Before any other step, verify deployment-tier setup. Action items from a postmortem should match the affected component's tier — recommending on-call rotations and chaos game days for a home-lab service is not a useful follow-up.

  1. Check COMPONENTS.md exists at the repo root. If missing, refuse to run and tell the PO:

    This project hasn't been onboarded yet. Run /onboard first — it produces COMPONENTS.md, which records each component's deployment tier. Postmortem action items need to match component tiers. See _shared/deployment-tier.md for the tier model.

    Do not proceed.

  2. Identify the affected component(s) from the incident.

  3. Look up tiers in COMPONENTS.md. If the affected component is missing, ask the PO to add it (with reasoning) before proceeding.

  4. Resolve cross-tier impact using strictest-wins by default — if the incident affected a startup-tier component, action items align to startup-tier even if the failure originated in a home-lab dependency.

  5. Inject tier context into every agent prompt. Every prompt below must additionally include:

    Read ~/.claude/skills/_shared/deployment-tier.md.
Affected components and tiers: [component] ([tier]), ...
Effective tier for action items: [tier]
Generate action items at the effective tier. Do not recommend enterprise practices (on-call rotations, formal chaos schedules, audit logging) on home-lab components unless the postmortem itself shows the home-lab framing was the root cause.

Model Selection

When spawning agents, pass model: explicitly per _shared/orchestration.md (Agent Model Selection). For this skill:

  • Fact-gathering and timeline construction: sonnet
  • Root cause analysis (SRE + relevant personas): opus — getting the root cause right matters more than getting it cheap

Read the full file on GitHub · 265 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. 2mo ago First seen · 265 lines · 48 tokens per session scan A d56fe8cede61

Subscribe to this mod's changes

postmortem is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 2,961 once invoked, about $0.0002 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-31.

Debugging
Related

postmortem compared with skills from other repositories

postmortem next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
postmortemMotWakorb/ai-agent-dev-teamSkill22mo agoMITA48Claude Code
systematic-debuggingopen-metadata/OpenMetadataSkill16ktodayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7ktodayMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319todayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2ktodayApache-2.0A15Claude Code, Codex
diagnosing-missing-recordingsPostHog/posthogSkill41ktodaynoneA76Claude Code, Codex
loop-engineeringhuytieu/COG-second-brainSkill1.3k15d agoMITA63Claude Code