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/iampawan/manifest/postmortemgit clone --depth 1 https://github.com/iampawan/ManifestWhat 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.00061 | $0.00610 |
| Opus 5 | $0.00030 | $0.00305 |
| Sonnet 5 | $0.00012 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
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 2d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postmortem
Closes the loop after a rollback — the one terminal state the pipeline
otherwise had no ending for. Run it once you've actually reverted the
feature (flag off / previous release redeployed); rollback-guard
recommends the rollback, you perform it, then this records and learns
from it.
Usage
/postmortem SC-005
/postmortem SC-005 "iOS crash on cold start at 10%"
What it does
- Confirms the feature was rolled back (asks if unclear — it won't write a postmortem for something still live).
- Reconstructs the timeline from the contract's cycle-time stamps, the
guard-*.mdreports, the deploy reports, and Sentry. - Writes
.manifest/contracts/<ID>.postmortem.md— blameless: what happened, the breached signal, contributing factors, what went well (detection caught it before full rollout), action items, re-ship plan. - Stamps the contract:
landed: rolled-back,rolledBackAt. - Reopens the work — a follow-up tracking issue (never closes it as
"done") or a route through
/fixfor small fixes. - Posts the verdict to Slack (thread + a top-level alert) and DMs the owner.
Learns from it. If a contributing factor is a code-shaped bug class
review could have caught, the postmortem proposes a candidate bug
pattern in reference/bug-patterns.candidates.md (staging — not yet
enforced). A maintainer reviews and, if it generalizes, promotes it into
reference/BUG-PATTERNS.md, where code-review then checks it on every
future diff — so the same class of bug can't ship twice. The human-accept
gate and the warning-until-proven default keep a new pattern from
blocking every PR. See the learning loop in BUG-PATTERNS.md.
Blameless by design
The postmortem describes systems, specs, and gaps — never a person as the cause. A rollback is information: detection worked and the blast radius was bounded. The feature still didn't land, and that's the thing to fix.
See also
/rollback-check <ID>//canary <ID>— the rollout-window health + ramp/contract verify <ID>— re-verify the new revision before re-promoting
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.
- 2d ago First seen · 56 lines · 61 tokens per session scan A eed139841301
postmortem is a command published in the GitHub repository iampawan/Manifest (5 stars, last pushed 20d ago), licensed MIT. It adds 61 tokens to every session and 610 once invoked, about $0.0003 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.