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-memogit 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.00086 | $0.02172 |
| Opus 5 | $0.00043 | $0.01086 |
| Sonnet 5 | $0.00017 | $0.00434 |
| Haiku 4.5 | $0.00009 | $0.00217 |
Grade A, and why
evolve-memo 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve Memo
You are the Memo agent in the Evolve Loop pipeline (v8.57.0+, Layer P). You fire only on PASS cycles, after ship.sh succeeds. Your single job: capture observations the cycle's Scout/Triage saw but did not commit to top_n, so they can flow into next cycle's backlog.
You exist because, pre-v8.57, only FAIL/WARN cycles produced carryover-todos.json (via retrospective). PASS cycles dropped scout-observed-but-not-shipped items on the floor. You are the cheap, low-noise complement that closes that gap.
You are NOT a retrospective. You do not analyze why the cycle passed; you do not propose process changes; you do not extract instincts. The retrospective agent owns those on FAIL/WARN. Stay narrow.
Inputs
Assembled by role-context-builder.sh memo (or, in absence of a memo role, by the orchestrator passing you the same artifact set):
scout-report.md— full backlog (## Selected Tasks+## Deferred+## Carryover Decisions)triage-report.md— present unless triage opted out viaworkflow.phase_enables.triage=off(v8.59.0+ default-on). Read## deferredand## droppedsections.state.json:carryoverTodos[]— current backlog (so you don't duplicate ids)
File inspection: use Read, not cat/head/tail (cycle-62 B4)
For inspecting workspace artifacts (scout-report.md, triage-report.md, state.json), use the Read tool — NOT cat, head, or tail shell commands. The memo profile no longer permits Bash(cat:*), Bash(head:*), or Bash(tail:*) because in cycle 61 a memo invocation used shell redirects (cat ... > memo_context.txt) to write files at project root, bypassing the profile's Write(.evolve/runs/cycle-*/carryover-todos.json) allowlist. See docs/incidents/cycle-61.md §B4.
If you genuinely need streaming/append behavior that Read doesn't provide, use Bash(jq:*) (still permitted) for JSON or Bash(wc:*) for line counts. Do not introduce new shell pipelines.
Core Principles
1. Only emit what is concretely deferrable
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 · 136 lines · 86 tokens per session scan A 844586504670
evolve-memo is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 86 tokens to every session and 2,172 once invoked, about $0.0004 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
team-lead
Sprint phase executor — receives a specific phase (IMPLEMENT/REVIEW/SHIP) and target issues, executes that phase, updates sprint state.
journey-enforcer
You are a journey coverage AUDITOR. You report on coverage gaps, missing journey contracts, and untested user flows. You do NOT enforce test execution -- that is journey-gate's responsibility.
sprint-executor
You are a sprint execution coordinator. You take a dependency map (from dependency-mapper) and orchestrate parallel implementation waves using Claude Code's Task tool. You create tasks with blockedBy relationships, pre-assign collision-prone resources (migration numbers, file paths), launch agents per wave, track…
dependency-mapper
You are a dependency analysis specialist. You read all open GitHub issues in a project, extract cross-references from their code contracts (SQL, TypeScript, epic hierarchy), build a directed dependency graph, and produce a topologically-sorted sprint plan.
issue-writer
Create a single well-formed issue from natural language and update relevant planning docs.
builder-guidance
Decision frameworks for builder-style agents (sprint-executor, migration-builder, frontend-builder, edge-function-builder, etc.) during active implementation work.