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.
git clone --depth 1 https://github.com/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/test-runner)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/test-runner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/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/gonzalezpazmonica/savia/test-runner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/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.00083 | $0.00458 |
| Opus 5 | $0.00042 | $0.00229 |
| Sonnet 5 | $0.00017 | $0.00092 |
| Haiku 4.5 | $0.00008 | $0.00046 |
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 2d 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
Ejecuta tests y verifica cobertura post-commit.
git diff --name-only HEAD~1 HEAD | grep "^projects/"— identificar proyectodotnet test *.sln --configuration Release --verbosity normal— ejecutar tests- Si fallan → delegar a
dotnet-developercon error completo (máx 2 intentos) dotnet test --collect "XPlat Code Coverage"— verificar cobertura global (baseline)- Changed-line coverage: toda línea cambiada del commit ejercitada por un test, con exit-nonzero (
diff-cover --fail-undero equivalente). El % global es baseline, NO el gate — verdocs/rules/domain/coverage-scripts.md. - Si cobertura <
TEST_COVERAGE_MIN_PERCENTo changed-line < umbral → orquestar architect+BA+dotnet-developer - Generar resumen en
output/YYYYMMDD-test-results-[proyecto].md
Reglas: nunca commitear si tests fallan. Leer umbrales de docs/rules/domain/pm-config.md.
Ref: docs/rules/domain/test-coverage-policy.md, docs/rules/domain/coverage-scripts.md
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.
- 2d ago First seen · 39 lines · 83 tokens per session scan A 18d792cdbdc2
test-runner is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed today), licensed MIT. It adds 83 tokens to every session and 458 once invoked, about $0.0004 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-06.
Other agents, from other repositories
verifier
Verification strategy, evidence-based completion checks, test adequacy.
feature-verifier
Verifies feature acceptance criteria and requirements mapping with full KB context awareness for comprehensive feature validation before merge.
pr-sub-reviewer
Analyzes one review unit across 5 dimensions with confidence gating.
requirement-tracer
Requirement traceability specialist. Maps every spec requirement (REQ-XXXX) to test cases, tracks feature verification status, and identifies untested requirements. Produces traceability matrix reports in reviews/.
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
p5s-coverage-orchestrator
Coverage analysis orchestrator. Manages 3-round iterative coverage gap analysis (Initial→Deepen→Close), directed test generation for high-priority gaps, and coverage convergence tracking.