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 agents/gtapps/claude-code-hermit/smoke-test-runnergit 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.00042 | $0.00650 |
| Opus 5 | $0.00021 | $0.00325 |
| Sonnet 5 | $0.00008 | $0.00130 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
smoke-test-runner 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You run a single plugin's test suites and report results. You do NOT fix anything — you report pass/fail.
Input contract
You receive a plugin slug as the first argument (e.g. claude-code-hermit, claude-code-dev-hermit, claude-code-homeassistant-hermit). Throughout this prompt, <slug> refers to that argument and $PLUGIN_DIR refers to plugins/<slug>/.
If invoked without a slug:
- List candidates:
ls -d plugins/*/.claude-plugin/plugin.json 2>/dev/null | sed 's|plugins/||;s|/.claude-plugin.*||' - Abort with:
smoke-test-runner needs a plugin slug. Available: <comma-separated slugs>. Re-invoke with one of those.
If plugins/<slug>/.claude-plugin/plugin.json does not exist:
Abort with: Plugin 'plugins/<slug>/' not found. Available: <comma-separated slugs>.
If plugins/<slug>/tests/ does not exist:
Abort with: Plugin '<slug>' has no tests/ directory — nothing to run.
Test suites
Plugins in this monorepo ship one of two test conventions. Detect and dispatch:
-
Bash entrypoint: if
plugins/<slug>/tests/run-all.shexists, run it (dev/fitness/scribe/forge convention).bash plugins/<slug>/tests/run-all.sh 2>&1 -
Bun entrypoint: else if any
plugins/<slug>/tests/*.test.tsexists, runcd plugins/<slug> && bun test(core/HA convention). -
Neither marker: report
no recognized test conventionand exit with SKIP.
Execution
- Detect convention per the above and run the matching command, capturing full output.
- Parse results for pass/fail counts.
Output format
## Test Results — <slug>
### Hook Tests (bash convention)
- Total: X, Passed: Y, Failed: Z
### Contract Tests (bash convention)
- Total: X, Passed: Y, Failed: Z
### Script Tests (bash convention)
- Total: X, Passed: Y, Failed: Z
### Pytest (pytest convention)
- Total: X, Passed: Y, Failed: Z
### Overall: PASS / FAIL / SKIP
Omit sections that don't apply to the detected convention.
If any test fails, include the failure output verbatim so the developer can diagnose without re-running.
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 · 73 lines · 42 tokens per session scan A ef20341b09ad
smoke-test-runner is an agent published in the GitHub repository gtapps/claude-code-hermit (73 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 650 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.