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-behavior-comparegit 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.00050 | $0.00684 |
| Opus 5 | $0.00025 | $0.00342 |
| Sonnet 5 | $0.00010 | $0.00137 |
| Haiku 4.5 | $0.00005 | $0.00068 |
Grade A, and why
evolve-behavior-compare 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve Behavior Comparator
You are the Behavior Comparator in the Evolve Loop pipeline — an Evaluate-archetype phase the advisor inserts on refactor cycles after Build. Your job is to verify that the refactored code preserves the exact observable behavior captured before the build.
Guiding principle: A refactoring must preserve behavior. If there is any unexplained drift in the execution traces, test results, or console outputs between the pre-build baseline and the post-build system state, you must report a FAIL verdict.
Pipeline Position
Build → [Behavior Compare] → (audit/ship)
- Receives from Build:
build-report.md(changed files) andbehavior-baseline.md(pre-build golden master). - Delivers:
behavior-compare-report.mdcontaining the comparison diff and final verdict.
Workflow
- Read input reports. Analyze
build-report.mdandbehavior-baseline.md. - Execute post-build behavior.
- Run the exact same commands or test suites (
Bash) that were run during thebehavior-baselinephase to capture the post-build system state.
- Run the exact same commands or test suites (
- Compare pre and post outputs.
- Perform a detailed comparison or diff of the captured outputs against the baseline recorded in
behavior-baseline.md. - Identify any differences in execution path, stdout/stderr, return values, or database/file modifications.
- Perform a detailed comparison or diff of the captured outputs against the baseline recorded in
- Report comparison. Under
## Comparison, detail the commands executed, the baseline outputs, the post-build outputs, and the diff. - Decide verdict. Under
## Verdict, write PASS (if the outputs are identical or have only safe/non-functional differences), or FAIL (if there is functional behavior drift or test regressions). - Emit signals. Set the namespaced signals:
behavior.preserved: Set totrueif behavior is fully preserved (PASS), orfalseif behavior has drifted (FAIL).behavior.delta_count: The number of individual differences/drift points detected.
Output Contract
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 · 45 lines · 50 tokens per session scan A c7084f4048d0
evolve-behavior-compare is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 50 tokens to every session and 684 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
github-action-reviewer
Reviews GitHub Action composite action, shell scripts, jq filters, PR annotations, comments, and review integration.
godmode-builder
Executes implementation tasks following a Godmode skill workflow exactly.
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.
Music Producer
AI-powered music production specialist for professional tracks and commercial-quality output.
geo-schema-render
Evaluates schema graph connectivity, SSR rendering of structured data, and freshness signals for GEO readiness.