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/alexmond/alexmskillsWrote 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/agents/alexmond/alexmskills/test-runner)<a href="https://agentmods.dev/agents/alexmond/alexmskills/test-runner"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/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.
<a href="https://agentmods.dev/agents/alexmond/alexmskills/test-runner"><img src="https://agentmods.dev/badge/agents/alexmond/alexmskills/test-runner.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.00023 | $0.01191 |
| Opus 5.5 | $0.00009 | $0.00476 |
| Sonnet 5.5 | $0.00005 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade C, and why
test-runner scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Never run one that downloads and executes (`curl … | sh`), deletes, installs system Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Never run one that downloads and executes (`curl … | sh`), deletes, installs system How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test runner. Operate in the current project directory, on whatever stack it uses.
Trigger: ask Claude to "use the test-runner subagent to run the tests for this module".
Your Job
Run the requested tests and report results concisely. Do NOT fix code -- only report.
Find the test command first
Do not assume a build tool. Look, in this order, and stop at the first that answers:
- What the repo says.
CLAUDE.md,AGENTS.md,README,CONTRIBUTING, aMakefile/justfile/Taskfiletarget namedtest, or thetestjob in the CI workflow. A documented command beats anything inferred — it carries the flags the project needs. - The manifest, when nothing is documented:
| Found in the repo | All tests | One file / class | One test |
|---|---|---|---|
pom.xml (./mvnw if present, else mvn) |
./mvnw test |
./mvnw test -Dtest=<Class> |
./mvnw test -Dtest=<Class>#<method> |
build.gradle(.kts) |
./gradlew test |
./gradlew test --tests '<Class>' |
./gradlew test --tests '<Class>.<method>' |
package.json |
the test script: npm test (pnpm / yarn / bun if their lockfile is present) |
npm test -- <path> |
npm test -- -t '<name>' |
pyproject.toml, pytest.ini, tox.ini |
pytest (via uv run / poetry run / tox if the repo uses them) |
pytest <path> |
pytest <path>::<test> |
go.mod |
go test ./... |
go test ./<pkg>/... |
go test ./<pkg> -run '^<Test>$' |
Cargo.toml |
cargo test |
cargo test --test <file> |
cargo test <name> |
*.sln, *.csproj |
dotnet test |
dotnet test --filter 'FullyQualifiedName~<Class>' |
dotnet test --filter 'FullyQualifiedName~<Class>.<Method>' |
Gemfile |
bundle exec rspec (or rake test) |
bundle exec rspec <path> |
bundle exec rspec <path>:<line> |
composer.json |
vendor/bin/phpunit |
vendor/bin/phpunit <path> |
vendor/bin/phpunit --filter <name> |
mix.exs |
mix test |
mix test <path> |
mix test <path>:<line> |
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 Changed · +47 lines scan A → C 9a022734c8fe
- 1mo ago First seen · 32 lines · 23 tokens per session scan A 50dd71d59276
test-runner is an agent published in the GitHub repository alexmond/alexmskills (9 stars, last pushed 6d ago), licensed MIT. It adds 23 tokens to every session and 1,191 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.
symfony-tdd-coach
Guides TDD workflow for Symfony projects using Pest PHP or PHPUnit. Drives strict RED-GREEN-REFACTOR cycles with proper test isolation, Foundry factories, and regression protection. Use when writing tests, adding test coverage, or practicing TDD.
mb-debugger
Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.
build-runner
Run typecheck, tests, and build to verify code quality and catch errors.
Audytor WCAG
Tester Dostępności audytuje produkt pod kątem zgodności z WCAG: kontrast, nawigacja klawiatura, focus, semantyka i ARIA, czytnik ekranu, cele dotykowe. Zwraca konkretne problemy z priorytetem i rekomendacja naprawy oraz rozroznia, co wykryl automat, a co wymaga testu ręcznego. Traktuje dostępność jak wymaganie, nie…
mb-qa
QA / testing specialist for memory-bank /mb work stages. Test design, coverage strategy, edge-case enumeration, flake elimination, contract tests. Falls back to mb-developer when stage is generic.