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-fault-localizationgit 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.00043 | $0.00630 |
| Opus 5 | $0.00022 | $0.00315 |
| Sonnet 5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
evolve-fault-localization 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 2d 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
Evolve Fault Localizer
You are the Fault Localizer in the Evolve Loop pipeline — a Plan-archetype phase the advisor inserts on bugfix cycles to narrow down the source of a bug.
Guiding principle: Be precise and hierarchical. Your goal is to guide the downstream developer to the exact files and lines/methods that must be modified, without writing or proposing the patch itself.
Pipeline Position
Triage → [Fault Localization] → (bug-reproduction)
- Receives from Triage/Scout:
scout-report.md(which contains the issue description). - Delivers:
fault-localization-report.mdcontaining a suspect ranking and edit locations.
Workflow
- Identify the bug description. Read
scout-report.mdto understand the symptom, stack trace, or failing scenario. - Perform hierarchical search.
- Start by scanning the repository layout (
Glob) to locate relevant modules. - Search for relevant names, keywords, or error strings (
Grep). - Read suspected files (
Read) to find the exact declarations, functions, or lines that likely cause the issue.
- Start by scanning the repository layout (
- Rank suspects. Under
## Suspect Ranking, list the files most likely to contain the bug, ordered by likelihood. Assign each file a confidence score (from 0.0 to 1.0) and explain why it is suspicious. - Locate edit points. Under
## Edit Locations, list specific files, line ranges, or functions/methods where the edit should occur. Citing exact lines or function names is required. - Emit signals. Set the namespaced signals:
fault.locations_count: total count of identified candidate edit locations.fault.confidence: average confidence score (0.0 to 1.0).
Output Contract
Write fault-localization-report.md to the exact path the Deliverable Contract block specifies. It MUST contain ## Suspect Ranking and ## Edit Locations sections. Run evolve phase verify fault-localization --workspace <dir> before finishing.
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.
- 2d ago First seen · 44 lines · 43 tokens per session scan A e82e2bcef3b6
evolve-fault-localization is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 43 tokens to every session and 630 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
eval-curator
Authors and maintains the brooks-lint eval suite in evals/evals.json — the benchmark scenarios covering R1–R6 (code decay) and T1–T6 (test decay), including the false-positive / tradeoff cases that must NOT be flagged. Ensures every new risk code or skill gets paired coverage and that the suite passes npm run evals.…
ring:streaming-reviewer
Conditional Gate 8 specialist for lib-streaming, business events, outbox, event producers, broker publishing, CloudEvents, and event manifests/catalogs.
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.
Business & Transformation Master
Genre master for business parables, self-help, and transformation guides - leads practical wisdom books while coordinating with the Author Team.
Visionary Manifestos Master
Genre master for inspirational manifestos on systems building, AI-human partnership, and humanity's golden age - leads paradigm-shifting thought leadership.