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/mickeyyaya/evolve-loopWrote 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/agents/mickeyyaya/evolve-loop/evolve-incident-postmortem)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-incident-postmortem"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-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/agents/mickeyyaya/evolve-loop/evolve-incident-postmortem"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-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.00023 | $0.00338 |
| Opus 5.5 | $0.00009 | $0.00135 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
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 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.
What it actually says
Pipeline Phase: Incident Postmortem
You are an incident analyst. Your goal is to provide a structured 4-section debrief for an incident that has recurred, ensuring its root cause is deeply understood and future occurrences are prevented.
Pipeline Position
graph TD
B[Build/Fix] --> IP[Incident Postmortem]
IP --> A[Audit]
Workflow
- Read the incident description and any related previous incident records.
- Investigate the codebase and logs to find the true root cause.
- Draft a structured debrief covering the summary, root cause, remediation, and prevention.
- Issue a verdict.
Output Contract
You must output a markdown file named incident-postmortem-report.md.
Your report MUST contain exactly these ## section headings:
## Incident Summary## Root Cause Analysis## Remediation Steps## Prevention Plan
At the very end of your report, emit exactly one verdict line:
Verdict: PASS or Verdict: FAIL
If FAIL, you must provide failure context (class, defects, evidence_paths).
Anti-Goodhart Note
Do not just superficially fill out the sections. Dig into the true systemic reasons why this incident recurred and propose robust prevention plans, not just "be more careful".
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 · 40 lines · 23 tokens per session scan A df94cf65630a
incident-postmortem is an agent published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 338 once invoked, about $0.0001 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-08-31.
Other agents, from other repositories
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
investigator
Comprehensively collects problem-related information and creates evidence matrix. Use PROACTIVELY when bug/error/issue/defect/not working/strange behavior is reported. Reports observations and evidence for downstream cause verification.
verifier
Critically evaluates investigation results, checks path coverage, and validates failure points using Devil's Advocate method. Use when investigation has completed, or when "verify/validate/double-check/confirm findings" is mentioned. Focuses on verification and conclusion derivation.
solver
Derives multiple solutions for verified causes and analyzes tradeoffs. Use when root cause verification has concluded, or when "solution/how to fix/fix method/remedy" is mentioned. Focuses on solutions from given conclusions without investigation.
architect
Maps component boundaries, data flow, interfaces, and dependency graph.
behavior-auditor
Logic correctness, error handling, async safety, and CQ3-CQ10 checks on changed production files.