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.
git clone --depth 1 https://github.com/latestaiagents/agent-skillsWrote 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/commands/latestaiagents/agent-skills/postmortem)<a href="https://agentmods.dev/commands/latestaiagents/agent-skills/postmortem"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/postmortem/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/commands/latestaiagents/agent-skills/postmortem"><img src="https://agentmods.dev/badge/commands/latestaiagents/agent-skills/postmortem.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.00018 | $0.00779 |
| Opus 5.5 | $0.00007 | $0.00312 |
| Sonnet 5.5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
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 1mo 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postmortem
Generate a comprehensive, blameless postmortem document following industry best practices.
What I Need
Provide incident details:
- Incident ID or description
- Timeline of events (I can pull from Slack/PagerDuty if connected)
- What was the root cause?
- What fixed it?
Or just say: /postmortem for yesterday's API outage and I'll gather details.
Generated Document Structure
# Postmortem: [Incident Title]
**Date:** YYYY-MM-DD
**Severity:** SEV-X
**Duration:** X hours Y minutes
**Author:** [Your name]
**Status:** Draft / Final
---
## Executive Summary
[2-3 sentence summary for leadership]
## Impact
- **Users Affected:** X,XXX
- **Revenue Impact:** $X,XXX (estimated)
- **SLA Breach:** Yes/No
- **Customer Notifications:** X sent
## Timeline (All times in UTC)
| Time | Event |
|------|-------|
| HH:MM | First alert fired |
| HH:MM | On-call acknowledged |
| HH:MM | Incident channel created |
| HH:MM | Root cause identified |
| HH:MM | Mitigation deployed |
| HH:MM | Service restored |
| HH:MM | Incident resolved |
## Root Cause Analysis
### What Happened
[Detailed technical explanation]
### Why It Happened (5 Whys)
1. Why did X fail? → Because Y
2. Why did Y happen? → Because Z
3. Why did Z occur? → Because...
4. Why... → Because...
5. Why... → **Root Cause**
### Contributing Factors
- [ ] Recent deployment
- [ ] Configuration change
- [ ] Capacity limits
- [ ] External dependency
- [ ] Missing monitoring
- [ ] Unclear runbook
## What Went Well
- Rapid detection (X minutes)
- Clear communication
- Effective collaboration
- [Other positives]
## What Could Be Improved
- Detection took X minutes (target: Y)
- Runbook was outdated
- Escalation path unclear
- [Other improvements]
## Action Items
| Priority | Action | Owner | Due Date | Ticket |
|----------|--------|-------|----------|--------|
| P0 | [Prevent recurrence] | @name | YYYY-MM-DD | JIRA-XXX |
| P1 | [Improve detection] | @name | YYYY-MM-DD | JIRA-XXX |
| P1 | [Update runbook] | @name | YYYY-MM-DD | JIRA-XXX |
| P2 | [Add monitoring] | @name | YYYY-MM-DD | JIRA-XXX |
## Lessons Learned
[Key takeaways for the team and organization]
---
*This postmortem follows blameless principles. We focus on systems
and processes, 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.
- 1mo ago First seen · 124 lines · 18 tokens per session scan A 9889d34aceb1
postmortem is a command published in the GitHub repository latestaiagents/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 779 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
fdk-fix
Fix all platform validation errors and lint errors in a Freshworks app. Runs fdk validate, identifies fatal errors and lint issues, applies fixes iteratively, and re-validates until all errors are resolved.
self-healing
Automatically detect and recover from errors without interrupting your flow.
fdk-react-create
Create a new Platform 3.0 React Meta app (default UI stack). Uses fdk create react-starter-template or react-meta skeletons with DEW components, metaConfig in manifest.json, and React Router.
fdk-refactor
Reduce function complexity in a Freshworks app to meet cyclomatic complexity ≤ 7 per function. Extracts helper functions, simplifies conditionals, and preserves behavior while improving code quality.
debugger
Systematic debugging with TodoWrite and Memory integration.
fw-setup-uninstall
Uninstall FDK completely — keeps Node.js and nvm (/fw-setup uninstall).