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/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/incident-postmortem)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/incident-postmortem"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/incident-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/hermeticormus/libresecops-claude-code/incident-postmortem"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/incident-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.00040 | $0.01214 |
| Opus 5.5 | $0.00016 | $0.00486 |
| Sonnet 5.5 | $0.00008 | $0.00243 |
| Haiku 4.5 | $0.00004 | $0.00121 |
Grade A, and why
incident-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 12d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/incident-postmortem
Generate a structured blameless post-incident review from incident timeline, actions taken, and outcomes.
Trigger
Use this command when:
- A security incident has been resolved and is ready for review
- A near-miss event occurred that warrants analysis
- Periodic review of past incidents for pattern identification
- Compliance requirements mandate documented incident reviews
Input
Required:
- Incident summary: What happened, when, and what was the impact
- Timeline: Sequence of events from detection through resolution
Optional:
- Actions taken: What containment, eradication, and recovery steps were performed
- Root cause: If already determined, the underlying cause
- Impact metrics: Duration, affected users, data exposure scope, financial impact
Process
Step 1: Timeline Construction
Build a complete, chronological timeline from all available information:
- Initial compromise (if known): When the attacker first gained access
- Dwell time: Period between compromise and detection
- Detection: How and when the incident was first identified
- Triage: When severity was classified and response activated
- Containment: When spread was stopped
- Eradication: When the threat was removed
- Recovery: When services were restored
- Resolution: When the incident was declared resolved
Key metrics to extract:
- Mean Time to Detect (MTTD): Time from compromise to detection
- Mean Time to Respond (MTTR): Time from detection to containment
- Mean Time to Recover: Time from containment to full service restoration
- Total incident duration: End-to-end from compromise to resolution
Step 2: Root Cause Analysis
Use the "5 Whys" technique to drill past symptoms to root causes:
- Why did the incident occur? (Proximate cause)
- Why was that possible? (Contributing factor)
- Why wasn't it prevented? (Control failure)
- Why didn't we detect it sooner? (Detection gap)
- Why wasn't there a faster remediation path? (Process gap)
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.
- 12d ago Changed · +5 lines · +40 tokens per session 059e7aa79302
- 1mo ago First seen · 162 lines · 0 tokens per session scan A 01f78be1dfeb
incident-postmortem is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 1,214 once invoked, about $0.0002 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 commands, from other repositories
verify
An independent recheck of a security assessment report that derives conclusions from its own evidence instead of accepting the original findings.
corporate-launcher
Build a secure, branded, organization-specific launcher around an AI coding CLI (Claude Code, Codex CLI, Gemini CLI, Cursor, or Cline) so the user can.
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.
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.