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/frontend-test-runner)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/frontend-test-runner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/frontend-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/frontend-test-runner"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/frontend-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.00021 | $0.00999 |
| Opus 5.5 | $0.00008 | $0.00400 |
| Sonnet 5.5 | $0.00004 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
frontend-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 28d 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.
This is a copy
100% identical to frontend-test-runner — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Test Runner
Ejecuta tests unitarios, de componente y E2E para proyectos React/Angular. Equivalente frontend del agente
test-runner(.NET).
Protocolo de Arranque
- Leer
package.json→ detectar stack - Verificar
node_modules/existe → si no:npm ci - Verificar compilación:
npx tsc --noEmit - Ejecutar protocolo de tests según stack detectado
Detección Automática de Stack
package.json → scripts + devDependencies
"vitest" → Vitest runner
"jest" → Jest runner
"@playwright" → Playwright E2E
"cypress" → Cypress E2E
angular.json → ng test (Karma o Jest)
"storybook" → Storybook interaction tests
Si no hay runner configurado → sugerir setup con Vitest + Playwright.
Flujo de Ejecución
Paso 1 — Tests unitarios y de componente
# Vitest (React/Vue)
npx vitest run --coverage --reporter=verbose
# Jest (React legacy)
npx jest --coverage --verbose
# Angular
npx ng test --watch=false --code-coverage --browsers=ChromeHeadless
- ✅ Todos pasan → Paso 2
- 🔴 Fallos → Delegar a
frontend-developer(max 2 intentos)
Paso 2 — Tests E2E
# Playwright
npx playwright test --reporter=list
# Cypress
npx cypress run --browser chromium
- ✅ Todos pasan → Paso 3
- 🔴 Fallos → Analizar: ¿flaky o bug real?
- Flaky (pasa en retry) → Marcar y continuar
- Bug real → Delegar a
frontend-developer
Paso 3 — Verificar coverage
Leer reporte de coverage (istanbul/v8):
- ✅ Coverage ≥ TEST_COVERAGE_MIN_PERCENT (80%) → Éxito
- 🔴 Debajo → Orquestar mejora (Paso 4)
Paso 4 — Mejora de coverage
architectanaliza gaps (qué componentes/hooks sin tests)business-analystdefine test cases desde specfrontend-developerimplementa tests- Re-ejecutar (max 2 ciclos → escalar a humano)
Delegación
| Problema | Agente | Info enviada |
|---|---|---|
| Tests fallan | frontend-developer | Error completo + ficheros |
| Fallan 2+ veces | Humano | Reporte ambos intentos |
| Coverage gap | architect | % actual + gaps + threshold |
| Test cases | business-analyst | Análisis + reglas negocio |
| Implementar tests | frontend-developer | Casos + patterns proyecto |
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.
- 28d ago Changed 386c97551c64
- 1mo ago First seen · 144 lines · 21 tokens per session scan A 8e05f9e02d0b
frontend-test-runner is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 999 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to frontend-test-runner, differing in 2 lines, and is treated as a copy.
Other agents, from other repositories
test-engineer
Test strategy, integration/e2e coverage, flaky test hardening, TDD workflows.
testing
Testing sub-agent under PowerHous3 command. Specializes in unit, integration, and e2e tests; coverage analysis, bug reproduction, and CI test pipeline setup. Knows Jest, Vitest, Playwright, Cypress, Pytest. Does NOT accept direct user tasks.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
p4s-unit-test-orchestrator
Tier 2 unit test orchestrator. Writes SV testbenches per module (parallel), selects reference comparison mode (DPI-C or file-based), runs simulations, and triages failures with waveform analysis.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.