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/evolve-lite-publishnpx skills add AgentToolkit/altk-evolve --skill evolve-lite-publishgit clone --depth 1 https://github.com/AgentToolkit/altk-evolveWrote 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/skills/agenttoolkit/altk-evolve/evolve-lite-publish)<a href="https://agentmods.dev/skills/agenttoolkit/altk-evolve/evolve-lite-publish"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/evolve-lite-publish.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.00018 | $0.01361 |
| Opus 5 | $0.00009 | $0.00681 |
| Sonnet 5 | $0.00004 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
evolve-lite:publish 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- publish — 97% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a Guideline
Overview
Publish one or more private guidelines from .evolve/entities/guideline/
into a configured write-scope repo. The entity is stamped with
visibility: public, owner, published_at, and source, moved into
the local clone of the write repo, and committed / pushed to the remote.
The same local clone is also what evolve-lite:sync pulls from — so you
and anyone else publishing to the same repo stay in sync.
Workflow
Step 1: Require a write-scope repo
Read evolve.config.yaml. If no entry has scope: write, tell the user:
"You need at least one write-scope repo to publish to. Run evolve-lite:subscribe with --scope write to set one up, then come back."
Then stop.
If identity.user is missing, ask for it and add it to the config.
Step 2: First-time setup
Ensure .evolve/ is gitignored at the project root:
grep -qxF '.evolve/' .gitignore 2>/dev/null || echo '.evolve/' >> .gitignore
Step 3: Pick the target write-scope repo
Filter repos: to entries with scope: write (Step 1 already aborted if
there were zero, so at least one exists here).
- Exactly one entry → use it as default.
- Multiple entries → show a numbered list with
notesand ask which to publish to.
Let {repo} be the chosen repo name and {branch} its configured branch (default main).
Step 4: List and select entities
List files in .evolve/entities/guideline/ and ask the user which to publish.
Step 5: Run publish script
For each selected file, run:
python3 .bob/skills/evolve-lite-publish/scripts/publish.py --entity "{filename}" --repo "{repo}" --user "{identity.user}"
Step 6: Commit and push
Build {names} as a comma-joined list of selected filenames, and
{guideline_paths} as a space-joined list of the corresponding
guideline/{filename} paths inside the clone (the files the publish
script just wrote).
git -C ".evolve/entities/subscribed/{repo}" add -- {guideline_paths}
git -C ".evolve/entities/subscribed/{repo}" commit -m "[evolve] publish: {names}"
git -C ".evolve/entities/subscribed/{repo}" push origin "{branch}"
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.
- 4d ago First seen · 143 lines · 18 tokens per session scan A 916e647c039d
evolve-lite:publish is a skill published in the GitHub repository AgentToolkit/altk-evolve (105 stars, last pushed yesterday), licensed Apache-2.0. It adds 18 tokens to every session and 1,361 once invoked, about $0.0001 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-30.
Other skills, from other repositories
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
memesh-review
Review and optimize the MeMesh memory database. Analyzes health score, finds stale/conflicting/redundant memories, shows work patterns, and suggests cleanup actions. Use when asked to "review memories", "check memory health", "clean up knowledge", or "what's in my memory".
elicit
Form-driven Socratic discovery — batch independent decision dimensions into one multi-select-capable form instead of N button-turns. Triggers on: scope this, discovery form, ask me everything at once, multi-select question.
roundtable
Convene the multi-LLM round table — Claude, Antigravity, and Codex deliberate a question; the user chairs promotion. Triggers on: roundtable, round table, convene the table, ask the table, what do the other models think, deliberate.
author-feature
Author a single-source feature page — a code-verified master that projects to .help kinds + docs pages, no API credits. Triggers on: author a feature page, single-source doc, new feature master, draft docs without an api.