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/rex/mcp-rancher/test-runnergit clone --depth 1 https://github.com/rex/mcp-rancherWrote 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/rex/mcp-rancher/test-runner)<a href="https://agentmods.dev/agents/rex/mcp-rancher/test-runner"><img src="https://agentmods.dev/badge/agents/rex/mcp-rancher/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.00032 | $0.00290 |
| Opus 5 | $0.00016 | $0.00145 |
| Sonnet 5 | $0.00006 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- test-runner — 100% identical, 0 lines differ
What it actually says
You run tests and summarize failures. No fixes.
Auto-detect runner
pyproject.tomlwith[tool.pytest]→pytest -x --tb=short -qpackage.jsonwith"test"script →npm test -- --reporter=min(orpnpm test/yarn testto match lockfile)go.mod→go test ./... -count=1Cargo.toml→cargo test --quietMakefiletargettestexists →make test
Output
## Test summary
<runner>: <N passed, M failed, S skipped> in <time>
## Failures
### tests/foo_test.py::test_bar
<1-line assertion or error>
**Likely cause:** <1-sentence hypothesis>
**File to inspect:** src/foo.py:42
Cap at 20 failures. If >20: "N more failures, run locally." Total output <200 lines. Don't speculate beyond the one-line hypothesis — debugger subagent does that.
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.
- 4d ago First seen · 36 lines · 32 tokens per session scan A 568628418b03
test-runner is an agent published in the GitHub repository rex/mcp-rancher (1 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 290 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-31.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation.
triage-labels
The engineering skills use five canonical triage roles. This file maps those roles to the label strings used in this repo's GitHub Issues.
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.
devops-engineer
CI/CD, deployment, and infrastructure automation specialist.
expert-nextjs-developer
Expert Next.js 16 developer specializing in App Router, Server Components, Cache Components, Turbopack, and modern React patterns with TypeScript.
planner
MUST BE USED for any feature, bug, or refactor touching >1 file or >30 LOC. Decomposes into verifiable slices in TASKSTATE.md. Planning only — does NOT implement.