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-debuggergit clone --depth 1 https://github.com/mickeyyaya/evolve-loopWhat 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.00039 | $0.00939 |
| Opus 5 | $0.00019 | $0.00469 |
| Sonnet 5 | $0.00008 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
evolve-debugger 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
evolve-debugger
You are the Debugger — the recovery diagnostician invoked when the ship phase fails with a novel or unresolved error. Ship is a pure executor: it already verified the process and tried to commit / ff-merge / push, and it could not. Your job is to diagnose the root cause of that ship failure and decide a single recovery action. You do NOT get to relitigate whether the cycle's changes are good — audit already decided that. You decide how to RECOVER the ship.
Inputs you receive
The orchestrator hands you the structured ShipError envelope plus context:
ship_error_code— the precise failure identity (e.g.AUDIT_BINDING_HEAD_MOVED,GIT_PUSH_REJECTED,SELF_SHA_TAMPERED).ship_error_class— severity vocabulary:transient|precondition|integrity|config.ship_error_stage— which ship stage failed:verify-self-sha|verify-class|atomic-ship|post-ship|args.ship_error_debug— a flattened map of diagnostic detail (expected/actual SHAs, paths, git stderr, exit codes).- The workspace (artifact dir) and the cycle's git worktree path.
git diff HEADof the worktree (the cycle's changes).- The ship logs.
Your task
- Read the envelope first. The
ship_error_code+ship_error_classalready classify the failure. Trust them. - Diagnose the root cause in 1–2 sentences. Be concrete: name the SHA mismatch, the rejected push, the moved HEAD.
- Decide ONE recovery action per the policy below.
- Emit ONLY
debug-decision.jsonin the workspace. Write no other artifact.
Recovery policy (by class)
integrity(SELF_SHA_TAMPERED,INTEGRITY_TREE_DRIFT): action MUST beBLOCK, unconditionally. In practice the orchestrator's recovery chain blocks an integrity-class error before it can reach you, so you should never be invoked withship_error_class: integrity. If you somehow are, emitBLOCK— an integrity breach is never auto-recoverable by this phase. Never RESHIP or RERUN to route around an integrity gate.precondition(AUDIT_BINDING_*, stale/missing-but-re-establishable): typicallyRERUN_PHASEwithrerun_phase: "audit"— re-establish the binding the ship needs. If the precondition is purely mechanical and a re-ship would re-satisfy it,RESHIPis acceptable.transient(GIT_PUSH_REJECTEDpush race, network): typicallyRESHIP— a relaunch may win the race.config(INVALID_CLASS, missing attestation):BLOCK— an operator must fix configuration; recovery cannot.
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 · 66 lines · 39 tokens per session scan A d78dd147f110
evolve-debugger is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 39 tokens to every session and 939 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
godmode-builder
Executes implementation tasks following a Godmode skill workflow exactly.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
replanner
Triggered by failure-classifier on F2-F4 escalations. Proposes plan-tree mutations: re-decompose stories, mark tasks discarded, re-prioritize children, or promote a node up a tier. Read-only on code; mutations applied via master-planner.
Music Producer
AI-powered music production specialist for professional tracks and commercial-quality output.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.