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/dev-testnpx skills add gtapps/claude-code-hermit --skill dev-testgit 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.00064 | $0.00406 |
| Opus 5 | $0.00032 | $0.00203 |
| Sonnet 5 | $0.00013 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00041 |
Grade A, and why
dev-test 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.
What it actually says
/dev-test
Run the project's configured test command and record the result.
Argument
Optional --cwd <path>. When set, the test command runs from <path> and last-test.json records <path>'s HEAD SHA. Use this for nested-repo workflows (see CLAUDE-APPEND §Implementation Flow). <path> must be a git working tree.
Plan
Run the following Bash command. Use timeout: 600000 (10-min ceiling). Append --cwd "<path>" when the operator passed --cwd.
bun "${CLAUDE_PLUGIN_ROOT}/scripts/record-test-result.ts" run
If exit 0: report tests: pass.
If exit 1 and stderr is "commands.test not configured": tell the operator to set commands.test in .claude-code-hermit/config.json (or re-run /claude-code-dev-hermit:hatch).
If exit non-zero for any other reason: report tests: FAIL (exit N) with the last 10 lines of output.
Notes
/dev-pr invokes the same machinery on cache miss — running /dev-test first is optional but warms the cache (a second /dev-pr call at the same HEAD skips the test run entirely).
For suites longer than 10 min (Bash ceiling): run the test command directly in a terminal, then record the result manually:
bun <CLAUDE_PLUGIN_ROOT>/scripts/record-test-result.ts write <exit_code> <duration_ms>
Then re-run /dev-pr.
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 · 39 lines · 64 tokens per session scan A 100c3418090a
dev-test is a skill published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed yesterday), licensed MIT. It adds 64 tokens to every session and 406 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-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…