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 skills add sgaunet/claude-plugins --skill run-testsgit clone --depth 1 https://github.com/sgaunet/claude-pluginsWrote 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.
[](https://agentmods.dev/skills/sgaunet/claude-plugins/run-tests)<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/run-tests"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/run-tests/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.
<a href="https://agentmods.dev/skills/sgaunet/claude-plugins/run-tests"><img src="https://agentmods.dev/badge/skills/sgaunet/claude-plugins/run-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00035 | $0.00623 |
| Opus 5.5 | $0.00014 | $0.00249 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
run-tests 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 1mo 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests Skill
Auto-detect the project's test runner from build files and run it. Returns pass/fail status with output.
Detection Logic
Probe for build/config files using first match wins -- but a config file existing does not mean the target inside it exists. Verify the named target before running it; when it is absent, fall through to the next matching row rather than reporting a failure.
| Trigger | Verify the target exists | Command | Fallback |
|---|---|---|---|
| Taskfile.yml | task --list-all | grep -qE '^\* test:' |
task test |
fall through to next row |
| Makefile | make -n test >/dev/null 2>&1 |
make test |
fall through to next row |
| go.mod | n/a | go test ./... |
-- |
| package.json | --if-present handles it |
npm test --if-present |
npx jest or npx vitest run |
| pyproject.toml / setup.py | n/a | python -m pytest |
-- |
| Cargo.toml | n/a | cargo test |
-- |
| None detected | n/a | Warn: "No test runner detected" and skip | -- |
A missing target is not a test failure. task test where no test task is
defined (this marketplace's own repo is exactly that case) exits non-zero for a
reason that has nothing to do with the code -- never take it into the
fix-and-retry loop below. Treat it as "this row does not apply", fall through to
language-native detection, and report "No test runner detected" only once every
row is exhausted.
Execution
- Detect the test runner using the table above, verifying the target exists before running it
- Run the detected command
- On success: report "Tests passed"
- On failure: display output, attempt fix (max 2 retries) — analyze failure, apply fix via Edit, re-run. Only for genuine test failures. If the command failed because the target or tool was absent, go back to detection instead of editing any code.
- Return final status (pass/fail) and output
Working Directory
If a working_directory context is provided (e.g., a worktree path), run all commands prefixed with cd <working_directory> &&. Otherwise, use the current directory.
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.
- 1mo ago First seen · 49 lines · 35 tokens per session scan A d32c3e96b747
run-tests is a skill published in the GitHub repository sgaunet/claude-plugins (17 stars, last pushed 3d ago), licensed MIT. It adds 35 tokens to every session and 623 once invoked, about $0.0001 per session on Opus 5.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
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
dotnet-verify
This skill should be used when working with Verify snapshot tests in .NET projects. Use when updating verified snapshots after intentional code changes, accepting new snapshots, discovering verify tests, or troubleshooting snapshot mismatches. Trigger phrases include "verify tests", "update snapshots", "accept…
testing-go
Writes tests following TDD (using go test, testify, and rapid) best practices. Use when writing unit tests, integration tests, or table-driven tests in Go.
testing-python
Writes tests following TDD Red-Green-Refactor (pytest + Hypothesis). Tests behavior, not implementation. Use when writing unit tests, integration tests, or property tests.
testing-rust
Writes tests following TDD (using cargo test, proptest, and insta) best practices. Use when writing unit tests, integration tests, or property-based tests in Rust.
testing-typescript
Writes tests following TDD (using vitest and @testing-library/react) best practices. Use when writing unit tests, integration tests, or component tests in TypeScript.