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/baphuongna/pi-crew/post-mortemnpx skills add baphuongna/pi-crew --skill post-mortemgit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/post-mortem)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/post-mortem"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/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.00014 | $0.00700 |
| Opus 5 | $0.00007 | $0.00350 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
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 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
post-mortem
The canonical engineering record of a bug fix. Written after debugging lands a real fix.
Required Inputs — Refuse to Draft Without These
- Reliable repro exists (deterministic or high-rate flake)
- Root cause is known (mechanism identified, not a hypothesis)
- Fix is identified (PR / commit / branch)
- Fix is validated (original repro now passes)
If any missing → list what's missing and stop. Do not draft.
Structure
1. Summary
What broke (user terms), what fixed it (one sentence). JIRA key, PR, owner. A reader who stops here should have the right answer.
2. Symptom
Concrete: test output, error message, log line. No paraphrase. What was actually observed.
3. Root Cause
The actual bug mechanism. Code identifiers welcome — function names, file paths, branch conditions. Walk the cause chain end-to-end.
4. Why It Produced the Symptom
Walk the chain so reader connects symptom to cause. Often non-obvious — bug is in X but visible failure is in Y.
5. Fix
What changed and why this addresses root cause. Link to PR/commit. If a previous fix attempt papered over the symptom, name it and explain what was wrong.
6. How It Was Found
Short. The debugging path:
- What repro made it deterministic
- What tools cracked it
- Hypotheses tried and rejected (with one-line reason each)
- The single experiment that confirmed the cause
7. Why It Slipped Through
CI gap? Latent code? Workload gap? Incomplete prior fix? Review miss? Be specific.
If honest answer is "no good reason" — say so. Blameless — describe the gap, not the person.
8. Validation
How we know the fix works:
- Original failing test now passes (test name)
- Customer workload now completes (workload identifier)
- Other affected configs/workloads also tested
If only one config validated, say so explicitly.
9. Action Items
What + owner + tracking artifact:
- Regression test added at . (Owner, test name)
- CI gap closed: . (Owner, ticket)
- Doc/runbook updated. (Owner, link)
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 · 97 lines · 14 tokens per session scan A 256a682b0d97
post-mortem is a skill published in the GitHub repository baphuongna/pi-crew (51 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 700 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-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…