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/test-runnpx skills add gtapps/claude-code-hermit --skill test-rungit 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.00035 | $0.00584 |
| Opus 5 | $0.00017 | $0.00292 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
test-run 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 3d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Run
Run plugin test suites and report a concise summary. Operates on a single plugin when given a slug; otherwise loops every plugin in plugins/.
Usage
/test-run — run tests for every plugin in plugins/ and report a per-plugin summary plus an overall PASS/FAIL.
/test-run <plugin-slug> — run tests for just that plugin.
Examples:
/test-run claude-code-hermit/test-run claude-code-homeassistant-hermit
Steps
0. Resolve target slugs
- If no slug arg was passed, run
bash scripts/test-all.shfrom the repo root (launches every plugin's suite in parallel; wall time is bounded by the slowest suite instead of their sum) and report its summary table directly — skip Steps 0-1 below entirely. - If a slug arg was passed, validate
plugins/<slug>/.claude-plugin/plugin.jsonexists. If not, abort with:Plugin 'plugins/<slug>/' not found. Available: <comma-separated slugs>.Then continue to Step 1 for that single plugin.
1. Run the suite (single-plugin arg only)
Plugins ship one of two test conventions. Detect and dispatch:
- Bash entrypoint — if
plugins/<slug>/tests/run-all.shexists (dev/fitness/scribe/forge convention):bash plugins/<slug>/tests/run-all.sh 2>&1 - Bun entrypoint — else if any
plugins/<slug>/tests/*.test.tsexists (core/HA/feed convention):cd plugins/<slug> && bun test 2>&1. - Neither marker — mark
no tests configuredand continue.
Capture full output. Extract pass/fail counts from the suite's summary line.
2. Report
Per-plugin block:
=== <slug> ===
Hook tests: X passed, Y failed (bash convention only)
Contract tests: X passed, Y failed (bash convention only)
Script tests: X passed, Y failed (bash convention only)
Bun tests: X passed, Y failed (bun convention only)
Plugin result: PASS / FAIL / SKIP
Final overall line:
Overall: PASS / FAIL (<n> passed, <m> failed, <k> skipped across <p> plugins)
If any test failed, include the failure details below the summary so the developer can act on them immediately.
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.
- 3d ago First seen · 60 lines · 35 tokens per session scan A 741786fc35a5
test-run is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 584 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…