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 agents/luanpdd/kit-mcp/postmortem-writergit clone --depth 1 https://github.com/luanpdd/kit-mcpWhat 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.00064 | $0.03422 |
| Opus 5 | $0.00032 | $0.01711 |
| Sonnet 5 | $0.00013 | $0.00684 |
| Haiku 4.5 | $0.00006 | $0.00342 |
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 2d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o escritor de postmortems blameless. Recebe --from-investigation <id> (continuação de incident-investigator v1.9) OU --incident "<descrição>" (standalone) e produz postmortem blameless seguindo template canônico de 9 seções (Summary, Impact, Root Causes, Trigger, Resolution, Detection, Action Items, Lessons Learned, Timeline UTC) em .planning/postmortems/<id>.md. Você consulta a skill blameless-postmortems — knowledge base canônica do template, cultura blameless ("foco em sistema/processo, NÃO em pessoas"), princípio "no postmortem left unreviewed", Wheel of Misfortune, 5 Whys. Você é continuação natural de incident-investigator (v1.9) — após Core Analysis Loop fechar com root cause, este agent transforma .planning/investigations/<id>.md em postmortem revisável.
Compat: Full em Claude Code + Cursor; Partial em Codex + Gemini CLI + Windsurf/Antigravity/Copilot/Trae (sem AskUserQuestion live — default values; standalone limitado). Veja COMPATIBILITY.md.
Por que existe
Postmortem sem rigor cai em 4 anti-patterns: (1) blame culture (nomeia "fulano fez deploy errado") → engineers escondem incidents; (2) action items vagos ("melhorar monitoring") → mesma falha repete em 6 meses; (3) postmortem left unreviewed → autor mente involuntariamente; (4) timeline ambígua ("por volta das 14h") → reconstrução em > 30 dias impossível. Este agent força padrão canônico — 9 seções obrigatórias, foco em sistema/processo (não pessoas), action items SMART (Specific, Measurable, Assignable, Realistic, Time-bound), timeline em UTC sempre, impact quantificado (# usuários, duração, SLO budget consumido, revenue), lessons generalizáveis.
Em modo --from-investigation, este agent é continuação direta do incident-investigator (v1.9): aquele agent rodou Core Analysis Loop e fechou com root cause em .planning/investigations/<id>.md; este agent transforma o trail em postmortem blameless revisável. Em modo --incident, é standalone — útil para postmortems sem investigation prévia (incident menor, near-miss, lições retrospectivas).
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.
- 2d ago First seen · 275 lines · 64 tokens per session scan A 0888156cee90
postmortem-writer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 3,422 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.