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/apurvbazari/claude-plugins/evolvenpx skills add ApurvBazari/claude-plugins --skill evolvegit clone --depth 1 https://github.com/ApurvBazari/claude-pluginsWhat 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.00051 | $0.08197 |
| Opus 5 | $0.00026 | $0.04098 |
| Sonnet 5 | $0.00010 | $0.01639 |
| Haiku 4.5 | $0.00005 | $0.00820 |
Grade A, and why
evolve 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.
How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve Skill — Apply Pending Drift Updates
You are applying accumulated tooling drift updates. This skill handles two drift sources: FileChanged drift (logged by hooks to .claude/onboard-drift.json, or the legacy .claude/greenfield-drift.json in projects onboarded before the rename) and plugin drift (detected by comparing the baseline in onboard-meta.json against currently-installed plugins).
Guard
Check both drift sources before deciding whether to proceed:
- Read
.claude/onboard-drift.jsonin the project root (falling back to the legacy.claude/greenfield-drift.jsonif only that exists — see § Legacy drift-file migration). Record whether it has entries. - Read
.claude/onboard-meta.json. If it containsdetectedPlugins.installedPlugins, run the plugin drift detection from Step 0 below. Record whether plugin drift was found.
If onboard-drift.json has no entries (or is missing) AND no plugin drift was detected AND no MCP drift was detected (Step 2c pre-check against .claude/onboard-mcp-snapshot.json) AND no skill frontmatter drift was detected (Step 2d pre-check against .claude/onboard-skill-snapshot.json) AND no agent frontmatter drift was detected (Step 2e pre-check against .claude/onboard-agent-snapshot.json) AND no output-style drift was detected (Step 2f pre-check against .claude/onboard-output-style-snapshot.json) AND no LSP drift was detected (Step 2g pre-check against .claude/onboard-lsp-snapshot.json) AND no built-in skills drift was detected (Step 2h pre-check against .claude/onboard-builtin-skills-snapshot.json) AND no research staleness was detected (Step 2i pre-check against onboard-meta.json.research):
No pending drift detected. Your AI tooling is in sync with your codebase.
FileChanged drift is logged automatically when dependencies, configs, or structure change. Plugin drift is detected by comparing installed plugins against the baseline in onboard-meta.json. MCP / skill / agent / output-style / LSP / built-in skills drift is detected by comparing live files against their respective snapshots in
.claude/. Research staleness is detected by re-checking the codebase against the stored research roster inonboard-meta.json.research.
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 · 355 lines · 51 tokens per session scan A 58650287841c
evolve is a skill published in the GitHub repository ApurvBazari/claude-plugins (0 stars, last pushed 26d ago), licensed MIT. It adds 51 tokens to every session and 8,197 once invoked, about $0.0003 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-31.
Other skills, from other repositories
cross-platform
Cross-platform development patterns for macOS, Windows, and Linux.
shell-scripting
Shell scripting best practices for cross-platform CLI tools.
c-notify
Send native macOS notification center alerts from the command line using terminal-notifier.
change-keybinding
Customize Warp keyboard shortcuts (keybindings, keymappings) by editing the user's keybindings.yaml file. Use when the user asks to remap a key combination, rebind an action, change a shortcut, or remove a default keybinding (e.g. "change ctrl+space to ctrl+s", "rebind the command palette to cmd+p", "remove the…
agent-add-mcp
Use this skill when helping users add MCP servers to their Warp configuration.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.