incident-postmortem-writer

incident-postmortem-writer is a skill for Claude Code, Codex from Amazon-Quick/Amazon-Quick-official-catalog. It costs 104 tokens per session (2,698 once invoked), scanned A, original, MIT-0.

An incident postmortem writer turns timelines, alerts, status updates, and debrief notes into a blameless account of a service incident.

In plain words
What is it for?
Use it to document the timeline, assess impact, analyze root and contributing causes, and assign follow-up actions.
Why use it?
It organizes scattered information into a shared record focused on impact, causes, and prevention rather than personal blame.

Skill for Claude CodeCodex

Which agent this was written for is unclear — body not stored (licence); the path alone says nothing.

Good fit Use it to document the timeline, assess impact, analyze root and contributing causes, and assign follow-up actions.

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/amazon-quick/amazon-quick-official-catalog/incident-postmortem-writer"><img src="https://agentmods.dev/badge/skills/amazon-quick/amazon-quick-official-catalog/incident-postmortem-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 104 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,698 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 unknown 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.00104 $0.02698
Opus 5 $0.00052 $0.01349
Sonnet 5 $0.00021 $0.00540
Haiku 4.5 $0.00010 $0.00270

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

Security

Grade A, and why

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

skills/software-engineering/incident-postmortem-writer/SKILL.md · 239 lines

The source is not reproduced here

Licensed MIT-0

The repository is licensed MIT-0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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 · 239 lines · 104 tokens per session scan A f4cd1a2ec8a7

Subscribe to this mod's changes

incident-postmortem-writer is a skill published in the GitHub repository Amazon-Quick/Amazon-Quick-official-catalog (48 stars, last pushed 7d ago), licensed MIT-0. It adds 104 tokens to every session and 2,698 once invoked, about $0.0005 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-09-03.

Related

Other skills, from other repositories

lark-shared

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

davidtoby/agent-skills · 49 tokens

litellm-vertex-proxy-repair

Diagnose and repair a local LiteLLM + Vertex AI proxy on macOS, especially when http://127.0.0.1:4000/ or /v1 is down, startup hangs at Waiting for application startup, /ui/login/ says Authentication Error, Not connected to DB!, or Prisma/PostgreSQL issues need to be isolated from the API proxy by splitting lite and…

davidtoby/agent-skills · 102 tokens

feishu-approval-fallback

Recover and harden Hermes Feishu command-approval flows when interactive card buttons fail, especially with Feishu error 200340 or callback-card sync issues. Use when Feishu approval buttons stop working, users must fall back to /approve or /approve always, approvalid types drift between int and string, or…

davidtoby/agent-skills · 82 tokens

feishu-websocket-stability

Stabilize Hermes Feishu websocket mode when reconnects are too slow, ping timing needs tuning, or multiple local gateways accidentally compete for the same Feishu appid. Use when Feishu websocket reconnect delays feel excessive, runtime websocket overrides appear ignored by the SDK, startup should fail fast on…

davidtoby/agent-skills · 85 tokens

github-auth-recovery

Recover from broken GitHub auth flows when git/gh operations fail. Use when gh is not logged in, HTTPS push/pull asks for credentials or errors like could not read Username, a repo remote is HTTPS but SSH may already work, or when GitHub operations fail and the agent needs a deterministic path to diagnose auth method…

davidtoby/agent-skills · 90 tokens

whisper-video-transcribe-workaround

When Whisper (CLI or Python) gets stuck on video files during transcription — output dir stays empty, process runs at low CPU/memory with no progress — the workaround is to extract audio first with ffmpeg, then transcribe the WAV. Use this when Whisper hangs or times out on a video file.

davidtoby/agent-skills · 69 tokens