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/gtapps/claude-code-hermit/hermit-evolvenpx skills add gtapps/claude-code-hermit --skill hermit-evolvegit clone --depth 1 https://github.com/gtapps/claude-code-hermitWhat 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.00047 | $0.03154 |
| Opus 5 | $0.00023 | $0.01577 |
| Sonnet 5 | $0.00009 | $0.00631 |
| Haiku 4.5 | $0.00005 | $0.00315 |
Grade A, and why
hermit-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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Evolve Hermit
Upgrade the project's hermit configuration after a plugin update.
Execution routing
Every run of this skill (interactive or unattended) delegates steps 0–9 to the claude-code-hermit:evolve-runner subagent, so the upgrade's transient churn (changelog slice, migration execution, file diffs) never lands in the calling session. The main loop keeps only step 10 (summary + operator notification).
Tool note:
claude-code-hermit:evolve-runneris a subagent — invoke it via the Agent tool, never the Skill tool. Theplugin:nameform it shares with skills does not imply the Skill tool.
- If you are running AS the
evolve-runnersubagent, skip this section and execute steps 0–9 directly (you are the delegate — do not re-dispatch). - Otherwise (main loop, any mode):
- Determine execution and delivery separately and remember both for step 10:
- Positional argument
unattended⇒ execution unattended, delivery automated-maintainer. - No
unattendedargument + an inbound<channel source="...">tag ⇒ execution unattended (never block onAskUserQuestion), delivery direct-channel-reply. - Otherwise ⇒ execution interactive, delivery inline.
Only the explicit
unattendedargument authorizes a proactive maintainer notification. A direct channel request must answer the channel that invoked it.
- Positional argument
- Bake the absolute plugin root to thread to the subagent (it cannot resolve it itself — the bare env var
$CLAUDE_PLUGIN_ROOTis not set at Bash runtime, and the value is empty inside subagents). Derive it from this skill's Base directory, which the harness injects in the skill invocation context as<plugin_root>/skills/hermit-evolve: strip the trailing/skills/hermit-evolveto getplugin_root. This works in both installed and--plugin-dirmodes. (In installed mode this equals the harness's${CLAUDE_PLUGIN_ROOT}substitution, which step 1 relies on; the Base-directory derivation is the mode-independent source.) Guard: confirm bothtest -f "<plugin_root>/skills/hermit-evolve/SKILL.md"andtest -f "<plugin_root>/skills/hermit-evolve/reference.md"— the subagent readsreference.mdfor steps 0–9, so a missing reference file is just as fatal as a missing SKILL.md. If either fails, abort — log"hermit-evolve aborted: plugin root unresolved; cannot dispatch evolve-runner."and stop. Do not dispatch with a broken path. - Dispatch the
claude-code-hermit:evolve-runnersubagent via the Agent tool. Pass the baked absolute plugin root and the report contract (below). Do not execute steps 0–9 yourself. - Go to step 10 with the subagent's returned report.
- Determine execution and delivery separately and remember both for step 10:
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.
- today Changed · +1 lines b18a1d4f543c
- 3d ago First seen · 115 lines · 47 tokens per session scan A 18c66510c222
hermit-evolve is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 3,154 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…