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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/commands/travisjneuman/.claude/test-suite)<a href="https://agentmods.dev/commands/travisjneuman/.claude/test-suite"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/test-suite/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/commands/travisjneuman/.claude/test-suite"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/test-suite.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.00007 | $0.01500 |
| Opus 5.5 | $0.00003 | $0.00600 |
| Sonnet 5.5 | $0.00001 | $0.00300 |
| Haiku 4.5 | $0.00001 | $0.00150 |
Grade A, and why
test-suite 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 12d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Suite Runner
Detects the project's test framework, runs tests at the specified scope, analyzes failures, reports coverage, and suggests missing test coverage.
Runs only when the user invokes it for that scope. The toolkit default is no testing: other work is validated by reviewing the diff and the code it touches.
Execution Flow
Step 1: Detect Test Framework
# Check for common test frameworks
[ -f "package.json" ] && grep -qE '"(jest|vitest|mocha|cypress|playwright)"' package.json && echo "NODE_PROJECT"
[ -f "pytest.ini" ] || [ -f "pyproject.toml" ] && grep -q "pytest" pyproject.toml 2>/dev/null && echo "PYTEST"
[ -f "go.mod" ] && echo "GO_TEST"
[ -f "Cargo.toml" ] && echo "CARGO_TEST"
Detected framework determines all subsequent commands.
| Framework | Test Runner | Coverage Tool |
|---|---|---|
| Jest | npx jest |
--coverage |
| Vitest | npx vitest run |
--coverage |
| Mocha | npx mocha |
npx c8 mocha |
| Pytest | pytest |
--cov |
| Go test | go test ./... |
-cover -coverprofile |
| Cargo test | cargo test |
cargo tarpaulin |
| Cypress | npx --no cypress run |
(via istanbul) |
| Playwright | npx --no playwright test |
(via istanbul) |
Browser runners use only the copy the project already has (npx --no); never let npx fetch Playwright, Cypress, or browser binaries.
Step 2: Run Tests by Scope
Scope: {{scope}} (default: all)
Unit Tests
# Node.js (Jest/Vitest)
npx jest --testPathPattern="(unit|__tests__)" 2>/dev/null || npx vitest run --dir tests/unit 2>/dev/null
# Python
pytest tests/unit/ -v 2>/dev/null || pytest -v -m unit 2>/dev/null
# Go
go test -short ./... -v
# Rust
cargo test --lib
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.
- 12d ago Changed · +4 lines 871cbca341fb
- 26d ago Changed · +1 lines 3b647b4e5f31
- 1mo ago First seen · 222 lines · 7 tokens per session scan A c1c6ba1f3a8b
test-suite is a command published in the GitHub repository travisjneuman/.claude (106 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 1,500 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
qa-automation
Set up a comprehensive test automation strategy.
test-gen
Generate comprehensive tests for a specified file with edge cases and error scenarios.
qa-e2e
End-to-End tests with Playwright or Cypress.
svelte:test-fix
Troubleshoot and fix failing tests in Svelte/SvelteKit projects, including debugging test issues and resolving common testing problems.
svelte:test-setup
Set up comprehensive testing infrastructure for Svelte/SvelteKit projects, including unit testing, component testing, and E2E testing frameworks.
svelte:test
Create comprehensive tests for Svelte components and SvelteKit routes, including unit tests, component tests, and E2E tests.