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 commands/latestaiagents/agent-skills/postmortemgit clone --depth 1 https://github.com/latestaiagents/agent-skillsWhat 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.00018 | $0.00779 |
| Opus 5 | $0.00009 | $0.00390 |
| Sonnet 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 3d 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.
- 3d 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 4mo ago), licensed MIT. It adds 18 tokens to every session and 779 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-31.
Other commands, from other repositories
fw-setup-use
Workspace FDK stack switch — nvm use from .nvmrc or explicit 10/9 (Node 24.11 vs 18); optional --write-nvmrc and --global flags.
fdk-migrate
Migrate a legacy Freshworks app from platform-version 2.3 (2.x), FDK 9.x, and Node 18 to Platform 3.0 with FDK 10.0.1 and Node 24.11.0. Transforms manifest, request templates, Crayons UI, and validates on the new toolchain. Does not install fdk/Node—use fw-setup (or prompt user to add it) per SKILL.md.
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.
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.
fw-setup-status
Check FDK and Node.js installation status (/fw-setup status); optional --verbose diagnostics.
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.