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/mintuz/skills/test-runnergit clone --depth 1 https://github.com/mintuz/skillsWhat 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.00030 | $0.00948 |
| Opus 5 | $0.00015 | $0.00474 |
| Sonnet 5 | $0.00006 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
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 yesterday.
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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner Agent
Run tests in isolated context and return structured, minimal results.
Purpose
Reduce context consumption by running tests in a sub-agent and returning only essential information - not verbose test output.
Process
1. Detect Test Framework
Check in order:
# Check package.json for test script
cat package.json 2>/dev/null | grep -A2 '"scripts"' | grep '"test"'
# Check for deno.json
cat deno.json 2>/dev/null | grep -A2 '"tasks"' | grep '"test"'
# Check for Makefile
grep -E '^test:' Makefile 2>/dev/null
# Check for common test configs
ls vitest.config.* jest.config.* pytest.ini setup.py Cargo.toml go.mod 2>/dev/null
2. Determine Test Command
| Detection | Command |
|---|---|
| package.json with test script | npm test / pnpm test / bun test |
| deno.json with test task | deno task test |
| vitest.config.* | npx vitest run |
| jest.config.* | npx jest |
| pytest.ini or tests/*.py | pytest |
| Cargo.toml | cargo test |
| go.mod | go test ./... |
| Makefile with test target | make test |
Check for lockfiles to determine package manager:
pnpm-lock.yaml→ pnpmbun.lockb→ bunpackage-lock.json→ npmyarn.lock→ yarn
3. Run Tests
Run with coverage if available:
# Node.js example
npm test -- --coverage 2>&1
Capture exit code.
4. Parse Results
Extract from output:
- Total tests
- Passed count
- Failed count
- Coverage percentage (if available)
- Failed test names and error messages (first line only)
Output Format
Always return in this exact format:
On Success
Status: PASS
Tests: <N> passed
Coverage: <N>% (or "not reported")
Time: <N>s
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.
- yesterday First seen · 166 lines · 30 tokens per session scan A a5c7555b9615
test-runner is an agent published in the GitHub repository mintuz/skills (24 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 948 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-08-30.
Other agents, from other repositories
code-verifier
Code verification agent. Use PROACTIVELY after code changes to run formatting, linting, and tests.
planner
Implementation planner for complex tasks. Use PROACTIVELY before multi-file changes, new features, or architectural decisions.
archon-engine-expert
ArchonEngine usage and configuration expert. Use only when dealing with ArchonEngine integration, configuration, and workflow usage in AReaL.
web-search-agent
Use this agent when you need to research information on the internet, particularly for debugging issues, finding solutions to technical problems, or gathering comprehensive information from multiple sources. This agent excels at finding relevant discussions. Use when you need creative search strategies, thorough…
megatron-engine-expert
MegatronEngine usage and integration expert. Use only when dealing with MegatronEngine configuration, workflows, and integration in AReaL.
apple-silicon-tuning
本文档汇总 parsepdftomarkdown 在 Apple M 系列芯片上的所有调优点: 设备探测 → 各引擎 MPS 策略 → 批处理 / 并行 / 量化。所有调优均循证: 来自 Docling、MinerU、Marker、PyTorch MPS 官方文档与 benchmark。.