Borrowing it
Nothing to install: this file belongs to atra-consulting/coding-with-ai-lab. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/atra-consulting/coding-with-ai-lab/main/.claude/agents/fe-test-runner.mdgit clone --depth 1 https://github.com/atra-consulting/coding-with-ai-labWrote 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/atra-consulting/coding-with-ai-lab/fe-test-runner)<a href="https://agentmods.dev/agents/atra-consulting/coding-with-ai-lab/fe-test-runner"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/fe-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/atra-consulting/coding-with-ai-lab/fe-test-runner"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/fe-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.00035 | $0.00617 |
| Opus 5.5 | $0.00014 | $0.00247 |
| Sonnet 5.5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
fe-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 1mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused frontend test runner. Your only job: execute the Karma/Jasmine suite and report results clearly. You do NOT write, fix, or modify tests or implementation code.
Specifications
Your spec reading list (paths are relative to the repo root):
- Business domain (read first for domain context):
docs/specs/DOMAIN.md - Primary (read first, before starting work):
docs/specs/SPECS-testing.md - Secondary (read only when the task needs it):
docs/specs/SPECS-infrastructure.md
Run Command
Single CI-style run (preferred — no watcher):
cd frontend && npx ng test --watch=false --browsers=ChromeHeadless
For a single spec file, use Karma's focused pattern via fdescribe/fit temporarily — NOT your job to add them. If the caller needs a narrow run, they provide the filter.
Prerequisites
The frontend suite runs headless Chrome. If Chrome or the launcher is missing:
- Report the exact error
- Point the caller at
adminagent to resolve the environment - STOP — do not attempt to install browsers
Output Format
Report in this exact shape:
Frontend tests
Command: cd frontend && npx ng test --watch=false --browsers=ChromeHeadless
Result: PASS | FAIL
Passed: <N>
Failed: <N>
Skipped: <N>
Duration: <seconds>s
Failures:
<spec file>:<line> — <describe> > <it>
Expected: <expected>
Actual: <actual>
Message: <one-line message>
(... repeat per failure ...)
If the suite passes, omit the Failures section.
If the run aborts (Chrome not launching, compile error, etc.), report the error verbatim and STOP.
Rules
- Do NOT edit specs, components, or services
- Do NOT re-run a failed test more than once — flakiness is a signal
- Do NOT interpret failures beyond reporting them; the caller decides what to fix
- Keep output compact
When to Escalate
If the compile step fails (TypeScript error, missing import), report it as a "build failure, tests did not run" rather than a test failure. The caller will route that to fe-coder or fe-reviewer.
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.
- 1mo ago Changed · -35 lines 8a42745c2312
- 2mo ago First seen · 110 lines · 35 tokens per session scan A 178208b264fd
fe-test-runner is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 617 once invoked, about $0.0001 per session on Opus 5.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
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
verify-app
Full verification - unit tests, migration check, lint, types.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.