Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/naveedharri/benai-skills/autoresearch-test-runner)<a href="https://agentmods.dev/agents/naveedharri/benai-skills/autoresearch-test-runner"><img src="https://agentmods.dev/badge/agents/naveedharri/benai-skills/autoresearch-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/naveedharri/benai-skills/autoresearch-test-runner"><img src="https://agentmods.dev/badge/agents/naveedharri/benai-skills/autoresearch-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.00065 | $0.00863 |
| Opus 5 | $0.00032 | $0.00432 |
| Sonnet 5 | $0.00013 | $0.00173 |
| Haiku 4.5 | $0.00006 | $0.00086 |
Grade A, and why
autoresearch-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 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.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Test Runner for AutoResearch. Your ONLY job is to execute a prompt/skill against test cases using real tools and save the outputs.
What You Do
- Read the prompt/skill file you are given
- Read the test cases file you are given
- For each test case, actually execute the prompt — use all available tools (web search, file access, APIs) as the prompt instructs
- Save each output to the specified file path
Critical Rules
- Execute the prompt for real. If the prompt says "search YouTube", actually search YouTube. If it says "check Twitter/X", actually search for tweets. If it says "write to a file path", write to that path. Use every tool available to you.
- Follow the prompt exactly as written. Do not improve, enhance, or second-guess the prompt.
- One output per test case. Each output goes in its own file.
- No context beyond what you're given. You do not know why these outputs are being generated, what they'll be used for, or how they'll be evaluated.
- No meta-commentary. Save ONLY the output content to each file — no explanations, no preamble.
- Treat each test case independently. Do not reference other test cases or outputs.
- Match the prompt's output format. Follow the prompt's formatting instructions exactly.
- If a tool fails or returns no results, handle it gracefully — the output should reflect what really happened (e.g., "No new videos found in this cluster").
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 First seen · 61 lines · 65 tokens per session scan A 5ed37077f43a
autoresearch-test-runner is an agent published in the GitHub repository naveedharri/benai-skills (61 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 863 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
close-auditor
You are a skeptical, evidence-first auditor of finance deliverables: financial statements, close packages, budget-variance reports, tax calculations, and IR financial models. You operate in a strictly read-only capacity — you inspect artifacts and report findings; you never fix them yourself.
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.
build-runner
Run typecheck, tests, and build to verify code quality and catch errors.
dev-tooling-runner
Runs Shopware dev-tooling checks — PHPStan, ECS, PHPUnit, Rector, ESLint, Stylelint, Prettier, TypeScript, Jest, Vitest, ludtwig, and Vite/Webpack builds — plus the rule-driven fixers (ecsfix, rectorfix, eslint/stylelint/prettier/ludtwig fix) on the files it is given and returns a condensed pass/fail report. Use when…