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 agentmods add skills/neurofoo/agent-skills/postmortemnpx skills add neurofoo/agent-skills --skill postmortemgit clone --depth 1 https://github.com/neurofoo/agent-skillsWhat 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 | $0.00042 | $0.00689 |
| Opus 5 | $0.00021 | $0.00345 |
| Sonnet 5 | $0.00008 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
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 3d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blameless Post-Mortem
Conduct a thorough, blameless analysis of an incident to understand what happened and prevent recurrence.
Instructions
Work through each section systematically. Focus on systems and processes, not individuals. The goal is learning, not blame.
Output Format
Executive Summary
Incident: [One-line description] Date/Time: [When it occurred] Duration: [How long] Severity: [Critical/High/Medium/Low]
Summary [2-3 sentence overview: what happened, impact, resolution]
Timeline
All times in [timezone].
| Time | Event | Actor |
|---|---|---|
| HH:MM | [What happened] | [Who/what did it] |
| HH:MM | [Detection] | [How it was noticed] |
| HH:MM | [Response action] | [Who responded] |
| HH:MM | [Resolution] | [What fixed it] |
Key Moments
- Trigger: [What initiated the incident]
- Detection: [How/when we knew something was wrong]
- Mitigation: [When bleeding was stopped]
- Resolution: [When fully resolved]
Impact
Customer Impact
- Users affected: [number]
- Duration of impact: [time]
- Symptoms experienced: [what users saw]
Business Impact
- Revenue impact: [if applicable]
- SLA/SLO breach: [yes/no, details]
Root Cause Analysis
Root Cause [The fundamental reason this happened—not the trigger, but why the trigger caused an incident]
Trigger [The immediate cause—what set things in motion]
Contributing Factors
| Factor | How It Contributed |
|---|---|
| [factor] | [explanation] |
Why Wasn't This Caught?
- Why didn't tests catch it?
- Why didn't monitoring alert earlier?
What Went Well
| What Worked | Why It Helped |
|---|---|
| [thing] | [explanation] |
What Went Poorly
| What Failed | Impact |
|---|---|
| [thing] | [impact] |
Action Items
Immediate (This week)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
Short-term (This month)
| Action | Owner | Due |
|---|---|---|
| [action] | [owner] | [date] |
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.
- 3d ago First seen · 126 lines · 42 tokens per session scan A a4e8d0d594e3
postmortem is a skill published in the GitHub repository neurofoo/agent-skills (111 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 689 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…