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/cpliakas/claude-code-engineering-leaders/conduct-postmortemnpx skills add cpliakas/claude-code-engineering-leaders --skill conduct-postmortemgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/conduct-postmortem)<a href="https://agentmods.dev/skills/cpliakas/claude-code-engineering-leaders/conduct-postmortem"><img src="https://agentmods.dev/badge/skills/cpliakas/claude-code-engineering-leaders/conduct-postmortem.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 | $0.00076 | $0.02152 |
| Opus 5 | $0.00038 | $0.01076 |
| Sonnet 5 | $0.00015 | $0.00430 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
conduct-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 4d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conduct Postmortem
Conduct a blameless incident postmortem for the incident described in
$ARGUMENTS. Collect evidence and produce a structured postmortem document.
Step 1 — Collect Available Evidence
If $ARGUMENTS is empty and there is no incident context in the current session,
ask the user to describe the incident before proceeding. Do not continue until
an incident description is provided.
Scan the current session context for:
- Error messages and stack traces
- Failed commands and their output
- Observed behaviors and timeline events
- Services and components involved
Read the incident description from $ARGUMENTS. If key facts are missing to
populate the timeline and impact section, prompt the developer for them before
proceeding:
- Severity: What was the user-facing or operational impact? (SEV-1 through SEV-4)
- Date/time: When did the incident occur (or when was it discovered)?
- Duration: How long until resolution?
- Services involved: Which components were affected?
- Impact metrics: Users affected, events disrupted, revenue lost, SLA violations?
Do not proceed to Step 2 until enough information exists to produce a credible timeline and quantified impact section.
Step 2 — Determine the Next POST ID
Check the DevOps Lead's project memory
(.claude/agent-memory/engineering-leaders-devops-lead/MEMORY.md) for a
configured postmortem directory path and ID format.
If a directory is configured:
- Read the index file (typically
README.md) in that directory - Find the highest
POST-NNNnumber in the index table - Set the next ID to that number + 1, zero-padded to 3 digits
If no directory is configured:
- Generate the postmortem document as output only (do not write to disk)
- Note in the output that the DevOps Lead's memory can be configured with a
postmortem_directorypath to enable automatic filing
The output filename convention is: POST-NNN-YYYY-MM-DD-<slug>.md
Where <slug> is a short, hyphenated description of the incident (e.g.,
migration-chain-failure, api-startup-crash, feed-parse-regression).
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.
- 4d ago First seen · 305 lines · 76 tokens per session scan A 5321c410ff97
conduct-postmortem is a skill published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 13d ago), licensed MIT. It adds 76 tokens to every session and 2,152 once invoked, about $0.0004 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
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
pdf-verification-cli
Verify PDF page count and content using command-line tools when Python libraries unavailable.