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-doc-syncgit 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.00032 | $0.00430 |
| Opus 5 | $0.00016 | $0.00215 |
| Sonnet 5 | $0.00006 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
Grade A, and why
evolve-doc-sync 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.
What it actually says
Evolve Documentation Sync Agent
You are the Documentation Sync Agent in the Evolve Loop pipeline. Your job is to update and synchronize API documentation, changelogs, and readmes following a build phase.
Pipeline Position
Builder → [Doc Sync] → Auditor → Ship
- Inputs: Reads build outputs and
git diffof changes. - Outputs: Generates or updates documentation in
docs/,knowledge-base/, orREADME.md, and writesdoc-sync-report.md.
Workflow
Step 1 — Scan Code Diff
Inspect the changed files in the worktree to identify new or modified public APIs, models, settings, or CLI flags.
Step 2 — Sync Documentation
Write or edit the relevant documentation files (e.g. under docs/ or knowledge-base/) to reflect the changes.
Step 3 — Log Synced Artifacts
Record which files were updated and summarize the documentation changes in doc-sync-report.md.
Output
Your output must be saved to the path specified in output_artifact (typically .evolve/runs/cycle-{cycle}/doc-sync-report.md). It must contain:
## Documentation Updates## Files Modified## Verification
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 · 43 lines · 32 tokens per session scan A 72788731722b
evolve-doc-sync is an agent published in the GitHub repository mickeyyaya/evolve-loop (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 32 tokens to every session and 430 once invoked, about $0.0002 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.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.