A skill that runs a project's automated tests, investigates failures, applies fixes, and runs the tests again. It supports common test tools across JavaScript, Python, Go, Rust, Java, Ruby, Shell, Elixir, and PHP projects.

It is for checking a full test suite or selected test files and getting the suite to pass.

It removes the need to identify the test command and manually repeat the diagnose-fix-test cycle.

test-runner — Skill for Claude Code by eugeniosegala

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.

Any agent

npx skills add eugeniosegala/claude-connoisseur --skill test-runner

Clone the repo

git clone --depth 1 https://github.com/eugeniosegala/claude-connoisseur

Made for: Claude Code.

Or install claude-connoisseur, the plugin that ships this one along with the rest of its 13 skills, 2 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/test-runner/github.svg)](https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/test-runner)

Your own site

<a href="https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/test-runner"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/test-runner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/eugeniosegala/claude-connoisseur/test-runner"><img src="https://agentmods.dev/badge/skills/eugeniosegala/claude-connoisseur/test-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,651 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00018	$0.01651
Opus 5	$0.00009	$0.00826
Sonnet 5	$0.00004	$0.00330
Haiku 4.5	$0.00002	$0.00165

Measured 11d ago against content hash 77e0dde5e16c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

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 11d 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.

skills/test-runner/SKILL.md · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Runner

Run the project's test suite (or specific test files), diagnose failures, fix them, and re-run until all tests pass.

Files and instructions: $ARGUMENTS

What to detect

Before running anything, determine the test framework and runner by inspecting the project:

JavaScript/TypeScript: jest, vitest, mocha, ava, tap, playwright, cypress — check package.json scripts, config files (jest.config.*, vitest.config.*, .mocharc.*), and dev dependencies
Python: pytest, unittest, nose2, tox — check pyproject.toml, setup.cfg, tox.ini, Makefile, or pytest.ini
Go: go test — check for *_test.go files
Rust: cargo test — check for Cargo.toml
Java/Kotlin: mvn test, gradle test — check pom.xml or build.gradle
Ruby: rspec, minitest — check Gemfile, .rspec, Rakefile
Shell: bats — check for *.bats files
Elixir: mix test — check mix.exs
PHP: phpunit — check phpunit.xml, composer.json

If multiple frameworks exist, run the one most relevant to the specified files — or all of them if no files are specified.

How to interpret arguments

The arguments are free-form and flexible. They may contain:

File references of any type and in any format: @service.test.ts, tests/unit/, test_*.py, *_test.go
Additional natural language instructions alongside file references, such as:
- "only run the unit tests"
- "run with coverage"
- "focus on the auth module tests"
- "run the tests I just changed"
- "fix the source code, not the tests"

When no arguments are provided, run the full test suite.

Examples

/test-runner — detect the framework and run the full suite
/test-runner @service.test.ts — run a specific test file
/test-runner tests/unit/ — run all tests in a directory
/test-runner only the tests related to authentication — find and run auth tests
/test-runner fix the source code, not the tests — fix implementation bugs instead of updating test expectations

Read the full file on GitHub · 137 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.

11d ago First seen · 137 lines · 18 tokens per session scan A 77e0dde5e16c

Subscribe to this mod's changes

test-runner is a skill published in the GitHub repository eugeniosegala/claude-connoisseur (9 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 1,651 once invoked, about $0.0001 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-31.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

test-runner