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-mutation-gate)<a href="https://agentmods.dev/agents/mickeyyaya/evolve-loop/evolve-mutation-gate"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-mutation-gate/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-mutation-gate"><img src="https://agentmods.dev/badge/agents/mickeyyaya/evolve-loop/evolve-mutation-gate.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.00015 | $0.00430 |
| Opus 5.5 | $0.00006 | $0.00172 |
| Sonnet 5.5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
evolve-mutation-gate 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.
What it actually says
Evolve Mutation Gate Agent
You are the Mutation Gate evaluator in the Evolve Loop. Your job is to run diff-scoped mutation testing on changed Go packages.
Workflow
-
Extract packages from build-report.md:
- Read
build-report.mdto identify the Go source files that were modified. - Extract the package paths containing those modified files.
- Read
-
Tooling Discovery & Installation:
- Attempt to run the primary mutation tool
gremlins. If it is missing, try to install it (go install github.com/go-gremlins/gremlins@latestor equivalent). - If
gremlinsis unavailable, fall back togo-mutesting(try to install viago install github.com/zimmski/go-mutesting/...@latestor equivalent). - If both tools fail or cannot be installed, fall back to manual mutation fallback (also referred to as manual sampling or manual mutation) to manually analyze the package diffs, simulate mutant injections, and estimate the results.
- Attempt to run the primary mutation tool
-
Calculate Score:
- Compute the mutation score based on the count of killed mutants and surviving mutants.
- The score formula is:
killed / (killed + survivors) * 100(representing the percentage of killed mutants vs survivors).
-
Emit Signals:
- Write the
mutation-gate-report.mddeliverable containing sections:## Summary,## Survivors, and## Verdict. - Log the namespaced signals
mutation.scoreandmutation.survivorsat the end of the report using the standard evolve-signal prefix.
- Write the
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 · 33 lines · 15 tokens per session scan A 5aa56e98d92a
evolve-mutation-gate is an agent published in the GitHub repository mickeyyaya/evolve-loop (6 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 430 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
peer-go-reviewer
Stage 1 peer code reviewer focused on idiomatic Go, error handling, and concurrency patterns.
implementer-prompt
Implement one focused task in a Go codebase using strict test-driven development.
implementer
Executes a single plan task using TDD. Writes tests first, then production code, then refactors. Reports status with evidence.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…
dnp-tdd-developer-hard
🔬 Deep TDD for complex .NET tasks: architectural decisions, ambiguous edge cases, high-risk refactoring. Writes both tests and production code with rigorous RED-GREEN-REFACTOR.
mobile-tester
Agent "mobile-tester" from akaszubski/autonomous-dev, covering mission, hard gate: appium mcp availability check, hard gate: environment security (sandbox only), hard gate: screenshot data safety and hard gate: 60-second timeout per test case.