Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add AgentToolkit/altk-evolve/plugin install evolve-liteWrote 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/unsubscribe)<a href="https://agentmods.dev/skills/agenttoolkit/altk-evolve/unsubscribe"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/unsubscribe/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/unsubscribe"><img src="https://agentmods.dev/badge/skills/agenttoolkit/altk-evolve/unsubscribe.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.00365 |
| Opus 5.5 | $0.00006 | $0.00146 |
| Sonnet 5.5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
unsubscribe 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.
This is a copy
86% identical to evolve-lite:unsubscribe — 13 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
Remove a Repo
Overview
Remove a configured repo (any scope) from evolve.config.yaml and delete
its local clone at .evolve/entities/subscribed/{name}/. Warn the user
before removing a write-scope repo since any unpushed local publish
commits will be lost.
Workflow
Step 1: List repos
Run:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --list
Show the repos to the user (including scope and notes) and ask which
one to remove.
Step 2: Confirm
Confirm deletion of .evolve/entities/subscribed/{name}/. If the repo has
scope: write, add a warning that unpushed local publish commits will be
lost.
Step 3: Run unsubscribe script
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name}
For a write-scope repo, the script refuses to remove the local clone
without --force so unpushed publishes can't disappear by accident:
python3 ${CLAUDE_PLUGIN_ROOT}/skills/evolve-lite/unsubscribe/scripts/unsubscribe.py --name {name} --force
Step 4: Confirm
Tell the user the repo was removed.
Notes
- This removes the entry from
evolve.config.yamlrepos:list - Deletes
.evolve/entities/subscribed/{name}/(the local clone, also the recall mirror) - The entities will no longer appear in recall
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 · 57 lines · 16 tokens per session scan A acbffe9e3ca4
unsubscribe is a skill published in the GitHub repository AgentToolkit/altk-evolve (124 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 365 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 86% identical to evolve-lite:unsubscribe, differing in 13 lines, and is treated as a copy.
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…