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/kimsanguine/AI_PMWrote 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/kimsanguine/ai_pm/postmortem)<a href="https://agentmods.dev/commands/kimsanguine/ai_pm/postmortem"><img src="https://agentmods.dev/badge/commands/kimsanguine/ai_pm/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/kimsanguine/ai_pm/postmortem"><img src="https://agentmods.dev/badge/commands/kimsanguine/ai_pm/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.00000 | $0.00506 |
| Opus 5.5 | $0.00000 | $0.00202 |
| Sonnet 5.5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 72 lines · 0 tokens per session scan A b4fa4b2f4e8b
postmortem is a command published in the GitHub repository kimsanguine/AI_PM (57 stars, last pushed 2mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 506 tokens. 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 commands, from other repositories
fire
FIRE orchestrator - Fast Intent-Run Engineering main entry point.
project_init
A command that starts tracking a project with ocul-pm by creating its project records and agent logging rules.
edit
An interview-style command for editing the trigger words used by existing personas. Personas are predefined viewpoints, such as a developer, designer, or lawyer, that guide how work is approached.
harness-operate
Full production operations workflow — KPI dashboard, reliability scan, cost review, improvement planning, knowledge extraction, decision pattern matching, and TK-to-instruction conversion. Use when an agent is live and needs a weekly/monthly operational review, or when running any individual operations step. Use…
harness-verify
Verify task/feature completion against CONDITIONALGO conditions in STATE.md. Syncs condition status (❌→✅) before any 'done' declaration. Use when marking a task complete, closing a sprint, or claiming a condition is met. Use --spec to run full Spec Compliance Review instead of STATE.md condition check.
cogs-sentinel
A command that runs the AI product cost check using provider prices, expected token use, call volume, and price per customer. It reports typical and high-use margins, the effect of free-user misuse, and a green, conditional-go, or red decision.