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 skills add mhmdreza-rafiei/agent-tools --skill postmortemgit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/postmortem)<a href="https://agentmods.dev/skills/mhmdreza-rafiei/agent-tools/postmortem"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/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/skills/mhmdreza-rafiei/agent-tools/postmortem"><img src="https://agentmods.dev/badge/skills/mhmdreza-rafiei/agent-tools/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.00074 | $0.00674 |
| Opus 5.5 | $0.00030 | $0.00270 |
| Sonnet 5.5 | $0.00015 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00067 |
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postmortem
Write the postmortem after an incident is stabilized. /recover stops the
bleeding; postmortem explains how the bleeding started and how to prevent it
next time. Blameless — focus on systems, not people.
When to use
After /recover has stabilized an incident; when the user says "write a
postmortem" or "post-incident report"; on /postmortem.
Commands
/postmortem— write from the incident timeline in context./postmortem <incident>— write a named incident./postmortem update— merge new findings into an existing postmortem.
Step 1 — Gather the timeline
- Read logs, chat threads, deploys, alerts from the incident window.
- If the timeline is unclear, ask for the start/end markers (max 2 questions).
Step 2 — Write the postmortem
Write to context/memory/incidents/<date>-<slug>.md. Use this shape — omit
empty sections:
# <incident> — postmortem (<date>)
## Summary
<1–3 lines: what happened, impact, duration>
## Impact
- Users / requests / data affected: <numbers>
- Duration: <window>
## Timeline
- <time> — <event>
- <time> — <event>
## Root cause
<the proximate cause, verified>
## Contributing factors
- <factor — e.g. missing alert, slow rollback, untested path>
## What went well
- <e.g. fast detection, clean rollback>
## Action items
- [ ] <action> — owner: <name/team> — by <date>
Step 3 — Verify
- Root cause is labeled verified or
> NEEDS VERIFICATIONif not confirmed. - Every action item has an owner and a date; no ownerless items.
- Blameless — no person named as a cause; only systems and processes.
Constraints
- Blameless: people don't cause incidents, systems do.
- Distinguish root cause (proximate) from contributing factors (conditions that made it worse).
- Do not invent impact numbers; mark unknowns.
- Trust runtime evidence over recollection.
Related artifacts
/context/recover(load first) — stabilized the incident this documents./context/remember— save the postmortem path for the next session.agents/devops/incident-responder— owns the response this reviews.rule/global/git-workflow— governs any fix commits referenced.
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 · 85 lines · 74 tokens per session scan A feaaf250d46b
postmortem is a skill published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 15d ago), licensed MIT. It adds 74 tokens to every session and 674 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.