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-diagnose-reference)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-diagnose-reference"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-diagnose-reference/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-diagnose-reference"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-diagnose-reference.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.00043 | $0.02713 |
| Opus 5.5 | $0.00017 | $0.01085 |
| Sonnet 5.5 | $0.00009 | $0.00543 |
| Haiku 4.5 | $0.00004 | $0.00271 |
Grade A, and why
evolve-diagnose-reference 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.
How it starts
The opening of the file, as written. The whole thing — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve Diagnose Reference (Layer 3 — on-demand)
Layer-3 on-demand reference. Adapted from mattpocock's 6-phase diagnose loop (mattpocock.com / Total TypeScript). Read this when a phase agent or orchestrator is facing a recurring failure and needs a systematic approach to trace and isolate the root cause. When diagnosing a WARN or FAIL cycle, come here before writing guesses into the retrospective. Do NOT read this file on every cycle — it is on-demand only.
Contents
- When to use this reference
- Phase summary
- Phase 1: Observe
- Phase 2: Hypothesize
- Phase 3: Instrument
- Phase 4: Reproduce
- Phase 5: Isolate / bisect
- Phase 6: Fix, verify, remove tags
- [DEBUG-XXXX] Tag Convention
- Evolve-Loop Examples
When to use this reference
| Trigger | Action |
|---|---|
| Audit returns FAIL and the root cause is unclear | Start at Phase 1 — do not skip to a fix |
Same WARN class appears in 3+ consecutive recentFailures entries |
Start at Phase 2 — symptom is already captured |
subagent-run.sh exits non-zero and stderr is empty |
Start at Phase 3 — instrument before re-running |
ship.sh exits non-zero with an audit SHA mismatch |
Use Example 2 below as the instrumentation template |
| Cycle cost is $0.00 and no ledger entry was written | Start at Phase 3 with the sandbox EPERM template (Example 3) |
Phase summary
| # | Phase | Core action |
|---|---|---|
| 1 | Observe | Capture the exact symptom: observed behavior vs. expected behavior. Record the precise error message, exit code, artifact path, and stack trace line. Do NOT hypothesize here. |
| 2 | Hypothesize | Generate 3–5 candidate root causes. Rank by likelihood. Write them down before testing any. |
| 3 | Instrument | Add [DEBUG-XXXX] tagged log/assertion points to test the top hypothesis. Instrument to test a specific hypothesis — NOT to "see what happens." |
| 4 | Reproduce | Reliably reproduce the failure with minimum steps. No fix is valid unless the failure can be triggered on demand. |
| 5 | Isolate / bisect | Eliminate half the candidate causes per iteration. Binary search to the smallest reproduction case. |
| 6 | Fix + verify + remove tags | Apply fix. Verify against the reproduction case. Search grep -r '\[DEBUG-XXXX\]' and remove all diagnostic artifacts before committing. |
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 · 246 lines · 43 tokens per session scan A 6c59891f8db5
evolve-diagnose-reference is an agent published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed today), licensed Apache-2.0. It adds 43 tokens to every session and 2,713 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-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.
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.