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 commands/mickeyyaya/evolve-loop/setupgit 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/commands/mickeyyaya/evolve-loop/setup)<a href="https://agentmods.dev/commands/mickeyyaya/evolve-loop/setup"><img src="https://agentmods.dev/badge/commands/mickeyyaya/evolve-loop/setup.svg" alt="Measured on agentmods" 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 | $0.00122 | $0.00202 |
| Opus 5 | $0.00061 | $0.00101 |
| Sonnet 5 | $0.00024 | $0.00040 |
| Haiku 4.5 | $0.00012 | $0.00020 |
Grade A, and why
setup 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 today.
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
Run the setup skill from the evo plugin (Skill tool id evo:setup); follow its SKILL.md instructions exactly.
Arguments: $ARGUMENTS
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.
- today First seen · 11 lines · 122 tokens per session scan A c754530bfffd
setup is a command published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed today), licensed Apache-2.0. It adds 122 tokens to every session and 202 once invoked, about $0.0006 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-09-03.
Other commands, from other repositories
splunk-ai-ml-toolkit-setup
Install, render, validate, and audit Splunk AI Toolkit / MLTK, Python for Scientific Computing, DSDL, anomaly workflows, and legacy anomaly app migration.
multi-backend
Backend-focused multi-model workflow (Research, Ideation, Plan, Execute, Optimize, Review).
prompt-audit
Discover and review LLM prompts in this codebase against the best-practices rubric. Reports findings and proposed diffs in the terminal — never edits without approval.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.