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 skills/agenttoolkit/altk-evolve/syncnpx skills add AgentToolkit/altk-evolve --skill syncgit clone --depth 1 https://github.com/AgentToolkit/altk-evolveWhat 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.00018 | $0.00245 |
| Opus 5 | $0.00009 | $0.00122 |
| Sonnet 5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
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.
This is a copy
97% identical to evolve-lite:sync — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Sync Repos
Overview
Pull the latest guidelines from every repo in evolve.config.yaml
repos: list — both scope: read (subscribe-only) and scope: write
(publish targets). Write-scope repos use a rebase strategy so any
unpushed local publish commits are preserved.
Workflow
Step 1: Run sync script
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/sync/scripts/sync.py
Step 2: Display summary
Show the script output to the user. If there are no repos configured,
tell them they can add one with /evolve-lite:subscribe. If there
are no changes, explain that everything is already up to date.
Notes
- Read-scope repos are mirrored exactly via
git fetch+git reset --hard - Write-scope repos use
git fetch+git rebaseso unpushed local publish commits are preserved - Sync results are logged to
.evolve/audit.log
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 35 lines · 18 tokens per session scan A 0351da4fbba3
sync is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed 7d ago), licensed Apache-2.0. It adds 18 tokens to every session and 245 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to evolve-lite:sync, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
agent-recall
Persistent compounding memory for AI agents. 5 default MCP tools: sessionstart, sessionend, remember, recall, check. Full surface (18 tools) available with --full flag. Two-verb model: inhale (sessionstart) and exhale (sessionend). Correction-first memory with decision trail tracking, watchfor warnings, palace rooms…
shelve
Offload a closed conversation topic (or a whole imported dialog) to the memory shelf as a Markdown episode with a validated digest. Use when a topic is finished, when context grows heavy, before compaction, or when the user asks to shelve/archive part of the conversation. M0 prompt-only version — the agent does the…
speckit-tasks
Generate an actionable, dependency-ordered tasks.md for the feature based on available design artifacts.
speckit-implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit-taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
speckit-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.