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/evolution-foundation/evo-nexusWrote 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/evolution-foundation/evo-nexus/mirror-retro)<a href="https://agentmods.dev/agents/evolution-foundation/evo-nexus/mirror-retro"><img src="https://agentmods.dev/badge/agents/evolution-foundation/evo-nexus/mirror-retro/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/evolution-foundation/evo-nexus/mirror-retro"><img src="https://agentmods.dev/badge/agents/evolution-foundation/evo-nexus/mirror-retro.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.00273 | $0.01919 |
| Opus 5.5 | $0.00109 | $0.00768 |
| Sonnet 5.5 | $0.00055 | $0.00384 |
| Haiku 4.5 | $0.00027 | $0.00192 |
Grade A, and why
mirror-retro 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 154 lines · 273 tokens per session scan A be937463147a
mirror-retro is an agent published in the GitHub repository evolution-foundation/evo-nexus (548 stars, last pushed 5mo ago), with no licence file. It adds 273 tokens to every session and 1,919 once invoked, about $0.0011 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-08-30.
Other agents, from other repositories
Channel Program Architect
Designs the partner program itself — the readiness gate that can answer 'not yet', which motions to run, partner unit economics on both sides, margin and SPIF design, and the rules of engagement that decide a contested deal.
Resource Allocator
Team capacity planning, skills-based assignment, and workload balancing.
engineering-manager
Use to turn an approved plan or goal into a sequenced delivery plan — decomposing work into tasks with acceptance criteria, estimating effort, mapping dependencies into parallelizable waves, and flagging risks and blockers. Pick this for any workflow step that plans who-does-what-and-when before code is written. Does…
planner
Turns a goal or spec into an ordered, dependency-aware task plan with acceptance criteria and a named critical path. Use when work needs sequencing before implementation starts.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
helm
Head of Product — product strategy, requirements, and engineering handoff via the Helm↔Apex interface.