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 thevibeworks/claude-code-docs --skill postmortem-reportgit clone --depth 1 https://github.com/thevibeworks/claude-code-docsWrote 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/thevibeworks/claude-code-docs/postmortem-report)<a href="https://agentmods.dev/skills/thevibeworks/claude-code-docs/postmortem-report"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/postmortem-report/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/thevibeworks/claude-code-docs/postmortem-report"><img src="https://agentmods.dev/badge/skills/thevibeworks/claude-code-docs/postmortem-report.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.00044 | $0.00427 |
| Opus 5.5 | $0.00018 | $0.00171 |
| Sonnet 5.5 | $0.00009 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
postmortem-report 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.
This is a copy
100% identical to postmortem-report — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Postmortem report
You build the PDF yourself, in your sandbox. There is no template. Design it so a director understands the event in one minute and an engineer can check every claim.
What it must contain
- A headline and a summary of three or four sentences.
- A table of pages: page id, service, root cause. Pages that share a root cause are one incident; mark the others as symptoms.
- At least one chart drawn from real data. Compute it in your script from
/mnt/session/uploads/app.log(for example p99 latency or error rate per minute for each paged service) and mark the deploys on it. - For each root cause: a timeline in UTC, the evidence that proves it, what was ruled out, and the fix.
- Action items, each with an owner team and a priority.
How to build it
- Python with matplotlib and pandas is installed.
matplotlib.backends.backend_pdf.PdfPageswrites multi-page PDFs. pandoc and LaTeX are there too. Use whichever you can do fastest. - The investigators' findings are in
/workspace/findings/*.json. Start from those instead of investigating again. - Save the result to
/mnt/session/outputs/postmortem.pdf. Only files under/mnt/session/outputs/reach the user. - Be quick: write one script, run it, and fix it only if it errors. Two to four pages. Do not render the PDF to images to inspect it.
- Keep everything inside the page margins: wrap the title and any long table cell instead of letting it run off the edge.
- Follow any postmortem conventions you find in team memory.
When it is built, tell the user the file name in one or two sentences. Do not paste the report into the chat.
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.
- 5d ago First seen · 28 lines · 44 tokens per session scan A cc5d26aff129
postmortem-report is a skill published in the GitHub repository thevibeworks/claude-code-docs (159 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 427 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to postmortem-report, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
PDF files: create, read, merge, fill, OCR, edit text.
wowerpoint
Turn one document into a kawaii NotebookLM slide deck. Use for "wowerpoint this", "make a deck about ", "turn this report into slides", or any request to render a single document as shareable narrative slides.
save-as-pdf
Reformat the current HTML design into a paginated, paper-ready PDF. The "Instant" export already gives the user a PDF at the design's native pixel size — this path is for when they want real pages.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
plan-deck-spec
A rulebook for creating Hai Lan Travel itinerary presentations in PowerPoint, a program for making slide decks. It defines the required slide order, content, formatting, research sources, and review checks.