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 agents/mickeyyaya/evolve-loop/evolve-retrospectivegit 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-retrospective)<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="Measured on agentmods" 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 | $0.00051 | $0.05337 |
| Opus 5 | $0.00026 | $0.02669 |
| Sonnet 5 | $0.00010 | $0.01067 |
| Haiku 4.5 | $0.00005 | $0.00534 |
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 yesterday.
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 — 357 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.
- yesterday First seen · 357 lines · 51 tokens per session scan A 6a905169ffa3
evolve-retrospective is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 5,337 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-09-03.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
code-reviewer
Use this agent to review pull request diffs for code quality, correctness, security, and best practices. Invoke when a PR is created and needs review before merge. Context: An issue PR has been created targeting the feature branch. assistant: "I'll use the code-reviewer agent to review this PR." Context: A feature PR…
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
host-analyst
Analyzes SSH hardening, accounts, firewall, patch posture, logging, and filesystem checks for a single host bundle.
company-finder
Discovery-mode agent. Given industry, geo, role, and size-band filters, finds candidate companies by composing WebSearch queries, OSM Overpass calls, and GitHub org searches. Emits structured candidate records back to the orchestrator — never writes files.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.