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 agents/floor/vlist/test-runnergit clone --depth 1 https://github.com/floor/vlistWhat 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.00035 | $0.00245 |
| Opus 5 | $0.00017 | $0.00122 |
| Sonnet 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 today.
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.
- today First seen · 32 lines · 35 tokens per session scan A 37a2ca854908
test-runner is an agent published in the GitHub repository floor/vlist (16 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 245 once invoked, about $0.0002 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-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…
bun-runtime-optimizer
Bun JavaScript runtime and bundler optimization specialist.
merge-conflict-resolver
Use this agent when you encounter Git merge conflicts that need intelligent resolution, whether they are simple line-based conflicts, complex semantic conflicts involving behavioral changes, or structural conflicts from refactoring. This agent should be used proactively when merge operations fail due to conflicts, or…
workflow-debugger
Use this agent when you need to debug Output SDK workflows in local development. Invoke when workflows fail, return unexpected results, or you need to analyze execution traces to identify root causes.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
speckit-constitution
Review or amend the project constitution. Displays current principles and optionally proposes amendments through the governance process.