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 skills/d-o-hub/github-template-ai-agents/test-runnernpx skills add d-o-hub/github-template-ai-agents --skill test-runnergit clone --depth 1 https://github.com/d-o-hub/github-template-ai-agentsWrote 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/skills/d-o-hub/github-template-ai-agents/test-runner)<a href="https://agentmods.dev/skills/d-o-hub/github-template-ai-agents/test-runner"><img src="https://agentmods.dev/badge/skills/d-o-hub/github-template-ai-agents/test-runner.svg" alt="Measured on agentmods" 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 | $0.00066 | $0.01105 |
| Opus 5 | $0.00033 | $0.00553 |
| Sonnet 5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00007 | $0.00111 |
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 3d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Runner
Expert skill for test execution and failure diagnosis.
Quick Start
Test Checklist:
- [ ] Environment configured
- [ ] Tests run or failures captured
- [ ] Failed tests diagnosed
- [ ] Coverage report generated
When to Use
- Running test suites
- Debugging failing tests
- Setting up CI/CD pipelines
- Analyzing test coverage
- Identifying flaky tests
Framework Commands
JavaScript
jest # Run all
jest path/to/test.ts # Specific file
jest --coverage # With coverage
jest --watch # Watch mode
Python
pytest # Run all
pytest tests/test.py # Specific file
pytest --cov=src # With coverage
pytest -v # Verbose
Rust
cargo test # Run all
cargo test test_name # Specific test
cargo test -- --nocapture # Show output
Go
go test ./... # Run all
go test -v ./... # Verbose
go test -cover ./... # With coverage
Bash
bats tests/ # Run all
bats tests/file.bats # Specific file
Diagnosing Failures
Step 1: Identify Error Type
| Pattern | Likely Cause | Action |
|---|---|---|
AssertionError: expected X got Y |
Logic error | Check implementation |
TimeoutError |
Async issue | Check async/await |
ModuleNotFoundError |
Missing dep | Install dependency |
panic: runtime error |
Go panic | Check nil/bounds |
Step 2: Isolate Test
pytest test.py::test_func -v # Python
jest --testNamePattern="test" # Jest
cargo test test_name # Rust
Step 3: Check Environment
pip list | grep pytest # Python
npm list jest # Node
# ./scripts/setup-test-db.sh # Test data (create if needed for project)
Coverage Analysis
Generate Reports
# Jest
jest --coverage --coverageReporters=text-summary
# Python
pytest --cov=src --cov-report=html
# Rust
cargo tarpaulin --out Html
# Go
go test -coverprofile=coverage.out ./...
go tool cover -html=coverage.out
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 198 lines · 66 tokens per session scan A 5dc49d2e1a51
test-runner is a skill published in the GitHub repository d-o-hub/github-template-ai-agents (2 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 1,105 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-31.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.