Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/JansenAnalytics/claudexnpx agentmods add skills/jansenanalytics/claudex/post-mortemWrote 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/jansenanalytics/claudex/post-mortem)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/post-mortem"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/post-mortem.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.00028 | $0.00599 |
| Opus 5 | $0.00014 | $0.00300 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
post-mortem 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
post-mortem
Generate structured post-mortems after incidents or failures: root cause analysis, timeline, impact assessment, prevention steps.
When to Use
- Analyzing why something broke
- Documenting incidents for the team
- Creating action items after failures
- Reviewing production issues
- Running blameless retrospectives
How It Works
- Gather incident details (what happened, when, who noticed)
- Run
generate-postmortem.shto create a structured document - Use
timeline-builder.shto construct a precise event timeline - Use
action-tracker.shto extract and track action items - Review references for blameless culture and root cause categories
Scripts
| Script | Purpose |
|---|---|
generate-postmortem.sh |
Generate a full post-mortem document from parameters |
timeline-builder.sh |
Build a formatted incident timeline from events |
action-tracker.sh |
Extract, list, and track action items from a post-mortem |
References
| File | Content |
|---|---|
postmortem-template.md |
Full post-mortem template with all sections |
blameless-guide.md |
Guide to running blameless post-mortems |
root-cause-categories.md |
Common root cause taxonomy |
Example Usage
# Generate a post-mortem document
bash scripts/generate-postmortem.sh \
--title "API Gateway Outage" \
--severity P1 \
--date "2024-01-15" \
--duration "2h 30m" \
--summary "API gateway became unresponsive due to connection pool exhaustion" \
--output postmortem-2024-01-15.md
# Build a timeline
bash scripts/timeline-builder.sh \
--add "14:00 Monitoring alerts fire for high latency" \
--add "14:05 On-call engineer acknowledges alert" \
--add "14:15 Root cause identified: connection pool exhaustion" \
--add "14:20 Fix deployed: increased pool size" \
--add "14:30 Service fully recovered" \
--output timeline.md
# Track action items
bash scripts/action-tracker.sh --extract postmortem-2024-01-15.md
bash scripts/action-tracker.sh --list postmortem-2024-01-15.md
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 · 70 lines · 28 tokens per session scan A edab2fe3dac5
post-mortem is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 28 tokens to every session and 599 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
analyzing-network-traffic-with-wireshark
Captures and analyzes network packet data using Wireshark and tshark to identify malicious traffic patterns, diagnose protocol issues, extract artifacts, and support incident response investigations on authorized network segments.
analyzing-memory-dumps-with-volatility
Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis…
k8s-incident-triage
Read-only Kubernetes incident triage using kubectl. Accepts natural language or structured input. Produces root-cause hypotheses, evidence, and next-step commands.
Debugging Strategies
Advanced debugging patterns for test failures covering root cause analysis, flakiness investigation, performance debugging, and systematic troubleshooting methodologies.
Flaky Test Doctor
Diagnose flaky test failures from Playwright reports, traces, and rerun history. Classify each failure as product, test, environment, data, or unknown with cited evidence and a proposed fix. Never auto-modifies code without opt-in.
Incident Response & Digital Forensics
IR playbook execution, evidence collection, forensic timeline analysis, memory forensics, and post-incident reporting following NIST SP 800-61 and SANS PICERL methodology.