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 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/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/skills/agenttoolkit/altk-evolve/evolve-lite-publish"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/evolve-lite-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00030 | $0.01470 |
| Opus 5.5 | $0.00012 | $0.00588 |
| Sonnet 5.5 | $0.00006 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- publish — 97% identical, 14 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish an Entity
Overview
Publish one or more private entities from .evolve/entities/<type>/ into a
configured write-scope repo. <type> is the directory the entity was saved
in: guideline for learned guidelines, or a native memory type (user,
feedback, project, reference) for entities saved by adapt-memory or the
EVOLVE.md save flow. The entity is stamped with
visibility: public, owner, published_at, and source, moved into
the local clone of the write repo under the same <type>/ directory, 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 the .md files in every type directory under .evolve/entities/, skipping
.evolve/entities/subscribed/ (other people's entities, never yours to
publish). Show each as {type}/{filename} 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}" --type "{type}" --repo "{repo}" --user "{identity.user}"
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 Changed · +6 lines · +12 tokens per session 794050c02ccd
- 1mo 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 (124 stars, last pushed yesterday), licensed Apache-2.0. It adds 30 tokens to every session and 1,470 once invoked, about $0.0001 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 skills, from other repositories
release-tag
Cut a release tag behind a real tier gate and cloud approval readback. The approval, task, approved commit, and resulting tag are bound; self-approval and HEAD drift fail closed. Prod prefixes remain refused.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
ops-release
OPS on-demand: This skill should be used when the user asks to "release the plugin", "publish ops…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
push-ci
Push to remote and monitor CI. Validates branch safety, executes git push WITH explicit user approval, then monitors CI run status via gh CLI. Use when: user says 'push', 'push and watch CI', 'ship it', 'push-ci'. Not for: committing (use /smart-commit), creating PRs (use /create-pr), merging (use /merge-prep).
bump-version
A procedure for changing a package and plugin version in several project files at the same time.