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-syncgit 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-sync)<a href="https://agentmods.dev/skills/agenttoolkit/altk-evolve/evolve-lite-sync"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/evolve-lite-sync/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-sync"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/evolve-lite-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 31 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00022 | $0.00243 |
| Opus 5.5 | $0.00009 | $0.00097 |
| Sonnet 5.5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00024 |
Grade A, and why
evolve-lite: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 1mo 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:
- sync — 97% identical, 6 lines differ
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 .bob/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.
- 1mo ago First seen · 35 lines · 22 tokens per session scan A 6e7b3afd79a7
evolve-lite:sync is a skill published in the GitHub repository AgentToolkit/altk-evolve (124 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 243 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
shelve
A conversation-archiving workflow that saves finished topics or imported conversations as Markdown records with a checked summary. A memory shelf is a collection of these saved conversation records.
triage-aging-prs
Drive an aging pull-request backlog to zero. Inventories every open PR, finds the STRUCTURAL blockers first (a required check that can never run, a reviewer that never fires, chronically red CI), triages every unresolved review thread in parallel and VERIFIES each finding against the code before fixing it, then merges…
review-comments
Systematically pull, categorize, and address all PR review comments — code change requests, questions, and suggestions. This skill fetches comments via gh api, groups them by file, implements fixes, handles disagreements diplomatically, and pushes a single commit. You should not try to handle PR review feedback…
commit
Automatically analyzes code changes and creates git commits with conventional commit messages when the user indicates they want to save their work, commit changes, or says 'commit this', 'save my changes', 'let's commit'. Auto-detects commit type, scope, and ticket reference from branch name.
merge-pr
Safely merge PR with verification and Linear integration. ALWAYS use when the user says 'merge the PR', 'merge this', 'ship it', or wants to merge an approved pull request. Runs tests, checks CI, verifies approvals, squash merges, cleans up branches, and moves Linear ticket to Done.
review-code
Review a branch's diff against its base for REAL defects only — bugs the diff makes certain, quoted CLAUDE.md/AGENTS.md violations, contradictions of recent git history, unaddressed prior-PR review comments, and in-code guidance the change ignores — each scored 0–100 and reported only at ≥80 confidence, ending in a…