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/dokkabei97/forged-claude-code/postmortem-writernpx skills add Dokkabei97/forged-claude-code --skill postmortem-writergit clone --depth 1 https://github.com/Dokkabei97/forged-claude-codeWrote 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/dokkabei97/forged-claude-code/postmortem-writer)<a href="https://agentmods.dev/skills/dokkabei97/forged-claude-code/postmortem-writer"><img src="https://agentmods.dev/badge/skills/dokkabei97/forged-claude-code/postmortem-writer.svg" alt="Measured on agentmods" 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.00040 | $0.00977 |
| Opus 5 | $0.00020 | $0.00489 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00098 |
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 6d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postmortem Writer - Blameless Incident Review
Overview
Documents failures so the team learns and the same mistake never happens twice. Blame people → they hide mistakes. Fix systems → they prevent mistakes.
1. When to Apply
| Trigger | Behavior |
|---|---|
| Production incident resolved | Full postmortem template |
| Project/launch failure | Project postmortem |
| "postmortem", "RCA" | Interactive postmortem builder |
2. Postmortem Template
# Postmortem: [Incident Title]
| Field | Value |
|-------|-------|
| **Date** | YYYY-MM-DD |
| **Severity** | P0 (Critical) / P1 (Major) / P2 (Minor) |
| **Duration** | [Start time] → [Resolution time] ([N] hours) |
| **Impact** | [Users affected, revenue lost, SLA breached] |
| **Author** | [Name] |
| **Reviewers** | [Names] |
| **Status** | Draft / Reviewed / Action Items Complete |
---
## Summary
[2-3 sentences: what happened, impact, how it was resolved]
## Timeline (All times in KST/UTC)
| Time | Event |
|------|-------|
| HH:MM | [First sign of issue] |
| HH:MM | [Alert triggered / User report] |
| HH:MM | [Investigation started by @name] |
| HH:MM | [Root cause identified] |
| HH:MM | [Fix deployed] |
| HH:MM | [Service fully restored] |
## Root Cause Analysis
### What Happened
[Detailed technical explanation of the failure chain]
### 5 Whys
1. **Why** did the service go down? → [Answer]
2. **Why** did that happen? → [Answer]
3. **Why** did that happen? → [Answer]
4. **Why** did that happen? → [Answer]
5. **Why** did that happen? → [Root cause]
### Contributing Factors
- [Factor 1 — not the root cause but made it worse]
- [Factor 2]
## What Went Well
- [Quick detection / response]
- [Effective communication]
- [Rollback worked as designed]
## What Went Poorly
- [Delayed detection]
- [Missing runbook]
- [Communication gaps]
## Action Items
| # | Action | Owner | Priority | Due | Status |
|---|--------|-------|----------|-----|--------|
| 1 | [Prevention measure] | @name | P0 | [date] | ⬜ |
| 2 | [Detection improvement] | @name | P1 | [date] | ⬜ |
| 3 | [Process change] | @name | P2 | [date] | ⬜ |
## Lessons Learned
- [Key insight for the team]
---
*This is a blameless postmortem. We focus on systems, not individuals.*
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.
- 6d ago First seen · 141 lines · 40 tokens per session scan A 82e05336d3a6
postmortem-writer is a skill published in the GitHub repository Dokkabei97/forged-claude-code (2 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 977 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-31.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
ax-cpp-agent-observability
Use when writing C++ code with axllm for agent tracing, centralized and multi-tenant usage accounting, action logs, runtime diagnostics, replay, and production debugging.
ha-logs
Self-service diagnostics — query Hope Agent's local SQLite databases (logs / sessions / background jobs) directly via the exec tool to investigate problems, analyze usage, and locate root causes. Trigger on: user reports something broken / failing / slow / stuck / not responding ('X 不工作', 'X 报错', 'X 卡住', '为什么 X 失败'…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.