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.
npx skills add Notysoty/openagentskills --skill incident-postmortem-writergit clone --depth 1 https://github.com/Notysoty/openagentskillsWrote 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.
[](https://agentmods.dev/skills/notysoty/openagentskills/incident-postmortem-writer)<a href="https://agentmods.dev/skills/notysoty/openagentskills/incident-postmortem-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/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.
<a href="https://agentmods.dev/skills/notysoty/openagentskills/incident-postmortem-writer"><img src="https://agentmods.dev/badge/skills/notysoty/openagentskills/incident-postmortem-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00024 | $0.02265 |
| Opus 5 | $0.00012 | $0.01132 |
| Sonnet 5 | $0.00005 | $0.00453 |
| Haiku 4.5 | $0.00002 | $0.00227 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Postmortem Writer
What this skill does
This skill turns a raw incident timeline, Slack thread dump, or bullet-point notes into a polished, blameless postmortem document. It structures the narrative, extracts action items, identifies contributing factors (not culprits), and formats everything into a document that can be shared with the team and used to prevent future recurrences. The output follows SRE best practices for blameless postmortems.
Use this immediately after an incident is resolved, while details are fresh, to produce the postmortem document without spending hours writing it from scratch.
How to use
Claude Code / Cline
Copy this file to .agents/skills/incident-postmortem-writer/SKILL.md in your project root.
Then ask:
- "Use the Incident Postmortem Writer skill. Here's the Slack thread from last night's outage: [paste thread]."
- "Write a postmortem for the database incident on March 14 using the Incident Postmortem Writer skill."
Provide:
- An incident timeline, Slack thread, or bullet-point notes describing what happened
- The approximate start and end time of the incident
- The user impact (how many users affected, what they experienced)
- Any action items already identified
Cursor
Add the instructions below to your .cursorrules or paste them into the Cursor AI pane. Paste the incident notes.
Codex
Paste the incident notes and ask Codex to follow the instructions below to produce the postmortem.
The Prompt / Instructions for the Agent
When asked to write a postmortem, follow these steps:
Principles to follow throughout
- Blameless — The postmortem must never assign blame to individuals. Systems and processes fail, not people. Use passive voice or process language: "the alert was not triggered" not "John missed the alert."
- Accurate — Represent the facts as given. Do not speculate beyond what the evidence supports.
- Actionable — Every section should lead toward specific improvements. Vague observations ("we should improve monitoring") must be turned into specific action items.
- Complete — Cover the full timeline from first symptom to full resolution, including any partial mitigations that were tried.
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.
- 9d ago First seen · 232 lines · 24 tokens per session scan A c4cecc4b548b
Incident Postmortem Writer is a skill published in the GitHub repository Notysoty/openagentskills (9 stars, last pushed 25d ago), licensed MIT. It adds 24 tokens to every session and 2,265 once invoked, about $0.0001 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.
Other skills, from other repositories
design-incident-response
Use when creating or improving an incident response process for a production system or operational team.
write-ops-runbook
Use when documenting a repeatable operational procedure that on-call engineers or operators must execute under pressure.
skill-builder
Automatically detect source types and build AI skills using Skill Seekers. Use when the user wants to create skills from documentation, repos, PDFs, videos, or other knowledge sources.
extract-source-sample
Given the path to a finished content-goose ad-run folder, extract everything that defines that ad — recipe shot list, VO script, characters, voices, world, atom-skills, master mp4 — and emit a source-sample.json in the exact shape the upload-ad-sample skill writes to the Goose Ads library. Also links every character…
comprehensive-enrichment
Enrich any person or company from any identifier — email, name, LinkedIn URL, domain, company name, Twitter/X handle. Use when asked to enrich, look up, or research a lead, contact, person, or company.
google-search-ads-builder
End-to-end Google Search Ads campaign builder. Performs deep keyword research (competitor SEO, review language mining, Reddit/HN community terminology, site audit), builds keyword architecture with funnel mapping and intent classification, creates ad group structure, generates headline/description variants, builds…