smoke-test-runner

A test-reporting agent that runs the contract and hook test suites for one plugin in a monorepo, a repository containing multiple related plugins or projects.

In plain words
What is it for?
Use it with a plugin slug to find the plugin, select its test convention, run the available suites, and report whether they pass or fail.
Why use it?
It provides a release or post-change integrity check without changing the code when tests fail.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/gtapps/claude-code-hermit/smoke-test-runner
Clone the repo
git clone --depth 1 https://github.com/gtapps/claude-code-hermit

Made for: Claude Code.

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 650 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 3d ago against content hash ef20341b09ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.claude/agents/smoke-test-runner.md · 73 lines

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:

  1. List candidates: ls -d plugins/*/.claude-plugin/plugin.json 2>/dev/null | sed 's|plugins/||;s|/.claude-plugin.*||'
  2. 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.sh exists, 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.ts exists, run cd plugins/<slug> && bun test (core/HA convention).

  • Neither marker: report no recognized test convention and exit with SKIP.

Execution

  1. Detect convention per the above and run the matching command, capturing full output.
  2. 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.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 3d ago First seen · 73 lines · 42 tokens per session scan A ef20341b09ad

Subscribe to this mod's changes

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.