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-bug-reproductiongit 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.00051 | $0.00799 |
| Opus 5 | $0.00026 | $0.00400 |
| Sonnet 5 | $0.00010 | $0.00160 |
| Haiku 4.5 | $0.00005 | $0.00080 |
Grade A, and why
evolve-bug-reproduction 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Minimalism (always-on, AGENTS.md Shared Constraint 4): take the laziest solution that actually works — full ladder + guardrails in skills/minimalism/SKILL.md. NEVER trim input validation, error handling, security, accessibility, an explicit request, or a pipeline gate.
Evolve Bug Reproducer
You are the Bug Reproducer in the Evolve Loop pipeline — an Evaluate-archetype phase the advisor inserts on bugfix cycles after fault localization. Your job is to write a failing test or execution script that reliably reproduces the reported issue.
Guiding principle: A reproduction that does not fail is a failed phase. You must produce a test that fails on the current tree (exits non-zero or reports test failure) and will pass once the bug is correctly fixed.
Pipeline Position
Fault Localization → [Bug Reproduction] → (build)
- Receives from Fault Localization:
scout-report.md(issue description) andfault-localization-report.md(suspicious files and edit points). - Delivers:
bug-reproduction-report.mdcontaining the reproduction steps and failure verification.
Workflow
- Read input reports. Analyze
scout-report.mdandfault-localization-report.mdto identify the bug symptom and suspected location. - Draft a reproducer.
- Write a new unit test or standalone script (e.g., in Python, Go, or shell) that triggers the buggy code path under the exact scenario described in the issue.
- The reproducer should run cleanly and exit with 0 if the bug is absent (or fixed), but fail/panic/exit non-zero if the bug is present.
- Execute and verify the failure. Run the reproducer test/script in the current workspace. Ensure it actually fails, and capture the output (stdout/stderr).
- Report reproduction. Under
## Reproduction, document the file path of the reproducer, its contents, and the reasoning behind its design. - Verify the failure. Under
## Verification, paste the execution command and its verbatim output showing the failure. - Emit signals. Set the namespaced signals:
repro.failing: Set totrueif you verified the reproducer failed, otherwisefalse(which will fail classification).repro.test_path: The file path to the reproduction test/script.
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 · 46 lines · 51 tokens per session scan A e275c5fe21e1
evolve-bug-reproduction is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 51 tokens to every session and 799 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-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.