agentmods.dev

evolve-fuzz-probe

An automated agent that tests changed Go code with many generated inputs, a technique called fuzz testing. It focuses on parsers, decoders, and functions that turn external data into program values, then writes a results report.

In plain words
What is it for?
Use it after changing Go functions that read, parse, decode, or unmarshal input, especially when checking for crashes and test coverage changes.
Why use it?
It can expose crashes and unexpected input-handling problems that example-based tests may miss. The report records crashes and newly reached code.

Agent

5 2d ago A scan 18 tokens original Apache-2.0
View the source file mickeyyaya/evolve-loop
Install

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.

agentmods
npx agentmods add agents/mickeyyaya/evolve-loop/evolve-fuzz-probe
Clone the repo
git clone --depth 1 https://github.com/mickeyyaya/evolve-loop
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 338 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00018 $0.00338
Opus 5 $0.00009 $0.00169
Sonnet 5 $0.00004 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured 2d ago against content hash b7ba0a82cc01, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evolve-fuzz-probe 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.

agents/evolve-fuzz-probe.md · 31 lines

What it actually says

Evolve Fuzz Probe Agent

You are the Fuzz Probe agent in the Evolve Loop. Your job is to run a short-budget Go-native fuzzing process on changed functions (especially parser, decoder, and unmarshal functions).

Workflow

  1. Identify fuzz targets:

    • Read the build-report.md to identify touched files and functions.
    • Scan for input-handling, parsing, decoding, or unmarshaling functions.

  2. Run Fuzzing:

    • Run Go-native fuzzing (go test -fuzz=. -fuzztime=60s) on the identified packages or functions.
    • If a crash occurs, write the crashers to the corpus and record details.

  3. Calculate Signals:

    • Record fuzz.crashers (number of unique crashes found) and fuzz.coverage_new (new coverage achieved).

  4. Emit Report:

    • Write the report fuzz-probe-report.md containing ## Target Functions, ## Fuzz Results, and ## Verdict sections.
    • Log the namespaced signals fuzz.crashers and fuzz.coverage_new using the standard format.
Changes

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.

  1. 2d ago First seen · 31 lines · 18 tokens per session scan A b7ba0a82cc01

Subscribe to this mod's changes

evolve-fuzz-probe is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 338 once invoked, about $0.0001 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.

Code reviewLanguagesTestingai-agentsai-pipelineautonomous-codingclaude-codeclaude-code-plugincode-quality
Related

Other agents, from other repositories

github-action-reviewer

Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.

fallow-rs/fallow · 26 tokens

godmode-builder

Executes implementation tasks following a Godmode skill workflow exactly.

arbazkhan971/godmode · 15 tokens

lead

Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.

nguyenthienthanh/aura-frog · 28 tokens

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.

nguyenthienthanh/aura-frog · 57 tokens

Music Producer

AI-powered music production specialist for professional tracks and commercial-quality output.

frankxai/agentic-creator-os · 15 tokens

spec-reviewer

Reviews design specifications for completeness, consistency, and implementability.

greglas75/zuvo · 16 tokens