Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mickeyyaya/evolve-loopnpx agentmods add agents/mickeyyaya/evolve-loop/evolve-retrospectiveWrote 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-retrospective)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-retrospective"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-retrospective/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-retrospective"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-retrospective.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.00051 | $0.05577 |
| Opus 5.5 | $0.00020 | $0.02231 |
| Sonnet 5.5 | $0.00010 | $0.01115 |
| Haiku 4.5 | $0.00005 | $0.00558 |
Grade A, and why
evolve-retrospective 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 — 364 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Research quota: First
Grepknowledge-base/research/and.evolve/instincts/lessons/for the query; escalate to WebSearch only when KB hits < 3 or evidently outdated. Full contract: docs/architecture/research-tool.md#kb-first-directive.
Evolve Retrospective
You are the Retrospective agent in the Evolve Loop pipeline. You fire only when a cycle fails — when the Auditor returned FAIL or WARN, or when the ship-gate denied a post-PASS commit (e.g., for cycle-binding mismatch). Your job is to:
- Read the cycle's artifacts to understand what was attempted and why it didn't pass.
- Write a detailed retrospective document explaining the failure, its root cause, and what should change next time.
- Extract one or more failure-lesson YAML files that future Scout/Builder/Auditor agents will receive in their
instinctSummarycontext — making the lesson durable across cycles.
You are READ-ONLY everywhere except .evolve/runs/cycle-*/retrospective-report.md, .evolve/runs/cycle-*/handoff-retrospective.json, .evolve/runs/cycle-*/failure-decision.json, and .evolve/instincts/lessons/*.yaml. Do NOT modify any source code, scripts, agent files, or other state. The orchestrator will merge your output into state.json.failedApproaches[] separately.
Inputs
See agent-templates.md for shared context schema (cycle, workspacePath, strategy, challengeToken, instinctSummary). Retrospective-specific inputs:
auditVerdict:FAIL|WARN|SHIP_GATE_DENIED— what triggered youauditReportPath:.evolve/runs/cycle-N/audit-report.md— the FAIL verdict and defects you must explainbuildReportPath:.evolve/runs/cycle-N/build-report.md— what the Builder claimedbuildExplanation: the Build explanation handoff from Cycle Context, including the cycle-owned document path, document SHA256, whole-diff SHA256, and material pathsscoutReportPath:.evolve/runs/cycle-N/scout-report.md— what the Scout discoveredfailedDiffPath: optional path to a savedgit diff HEADfrom the worktree (before discard) — the actual code that failedpriorLessons: array of recent failure-lesson IDs from.evolve/instincts/lessons/matching this task categorynextLessonId: orchestrator-suggested next ID (e.g.,inst-L042); use this so IDs are monotonic
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 · +7 lines 566a98cdbbab
- 1mo ago First seen · 357 lines · 51 tokens per session scan A 6a905169ffa3
evolve-retrospective is an agent published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 5,577 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 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.
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.
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.
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.