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/random6913/claude-code-superkit/test-runnernpx skills add RaNDoM6913/claude-code-superkit --skill test-runnergit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/test-runner)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/test-runner"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/test-runner.svg" alt="Measured on agentmods" 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 | $0.00024 | $0.00893 |
| Opus 5 | $0.00012 | $0.00447 |
| Sonnet 5 | $0.00005 | $0.00179 |
| Haiku 4.5 | $0.00002 | $0.00089 |
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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests
Auto-detect the project's test runner and execute tests.
Target
Parse the user's request to determine scope and parameters. Accepted formats: backend, frontend, e2e, all, --coverage.
Step 1 — Detect Test Runner
Scan the project root and subdirectories for stack markers:
| Marker | Test Command | Stack |
|---|---|---|
go.mod |
go test ./... -count=1 |
Go |
package.json + vitest config |
npx vitest run |
Vitest |
package.json + jest config |
npx jest |
Jest |
package.json + playwright config |
npx playwright test |
Playwright (e2e) |
pyproject.toml / pytest.ini / conftest.py |
pytest |
Python (pytest) |
pyproject.toml with [tool.unittest] |
python -m unittest discover |
Python (unittest) |
Cargo.toml |
cargo test |
Rust |
pom.xml |
mvn test |
Java (Maven) |
build.gradle |
./gradlew test |
Java/Kotlin (Gradle) |
Makefile with test target |
make test |
Makefile |
If a Makefile with a test target exists and the stack has one, prefer make test as it may include additional setup.
Step 2 — Determine Scope
Based on the user's request:
backend (or empty — default)
Run backend tests only:
- Go:
go test ./... -count=1 -short - Python:
pytest tests/orpytest - Rust:
cargo test - Java:
mvn test/./gradlew test
If the project is a monorepo, cd into the backend directory first (detect by backend/, server/, api/, or src/ containing the go.mod/pyproject.toml).
frontend
Run frontend tests:
- Vitest:
npx vitest run - Jest:
npx jest
If the project is a monorepo, cd into the frontend directory first (detect by frontend/, web/, client/, or app/ containing package.json).
e2e
Run end-to-end tests:
- Playwright:
npx playwright test - Cypress:
npx cypress run - pytest + selenium:
pytest tests/e2e/
all
Run all detected test suites sequentially. Report results for each.
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.
- yesterday First seen · 94 lines · 24 tokens per session scan A e83af04c0747
test-runner is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 893 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-09-03.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-spec-guardian
Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/.schema.json), or the conformance fixture seed…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
pr-description-skill
Use this skill to write the PR description (PR body) for any pull request opened against microsoft/apm. Produces one self-sufficient GitHub-Flavored Markdown artifact: TL;DR, Problem (WHY), Approach (WHAT), Implementation (HOW), 1-3 validated mermaid diagrams, explicit trade-offs, validation evidence, and a…