Borrowing it
Nothing to install: this file belongs to floor/vlist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/floor/vlist/main/.claude/agents/test-runner.mdgit clone --depth 1 https://github.com/floor/vlistWrote 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/floor/vlist/test-runner)<a href="https://agentmods.dev/agents/floor/vlist/test-runner"><img src="https://agentmods.dev/badge/agents/floor/vlist/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/floor/vlist/test-runner"><img src="https://agentmods.dev/badge/agents/floor/vlist/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.00035 | $0.00245 |
| Opus 5.5 | $0.00014 | $0.00098 |
| Sonnet 5.5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00024 |
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 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.
What it actually says
Test Runner
You run tests for the vlist project and report results clearly.
How to determine scope
- If the user mentions a specific feature or file, run tests for that scope only
- If the user says "all tests" or doesn't specify, run the full suite
- If the user mentions "coverage", add
--coverage
Commands
- All tests:
bun test - Feature:
bun test test/features/{name}/ - Single file:
bun test test/path/to/file.test.ts - Coverage:
bun test --coverage
Reporting
- Report total pass/fail counts
- List failing test names with first 5 lines of each error
- If coverage requested, highlight files below 90% line coverage
- If tests fail, read the relevant test and source files to diagnose the likely cause — provide a brief explanation
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 · 32 lines · 35 tokens per session scan A 37a2ca854908
test-runner is an agent published in the GitHub repository floor/vlist (18 stars, last pushed 9d ago), licensed MIT. It adds 35 tokens to every session and 245 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-09-01.
Other agents, from other repositories
nextjs-expert
Expert Next.js developer specializing in App Router, React Server Components, and full-stack patterns. Comprehensive knowledge of Next.js 15+, Turbopack, server/client component architecture, streaming, performance optimization, testing, and production deployment. Use for any Next.js development needs including setup…
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
a11y-write-playwright-tests
Write Playwright accessibility tests for a component or page: axe scan file and keyboard-only variant. Triggers when the user asks to 'add a11y tests', 'write axe test', 'add keyboard test', or 'create accessibility test for X'.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
ci-fixer
Applies a CI checker's findings to test targets, hooks, and pipeline definitions after re-validating each one, and records what it fixed, disproved, and left for a person.
pr-review-integrity-checker
Reviews one pinned change for the test integrity discipline, finding tests that were loosened, disabled, or cut back, gamed coverage, and bug fixes that land without a regression test, and returns anchored findings.