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-reviewer.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-reviewer)<a href="https://agentmods.dev/agents/atra-consulting/coding-with-ai-lab/fe-test-reviewer"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/fe-test-reviewer/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-reviewer"><img src="https://agentmods.dev/badge/agents/atra-consulting/coding-with-ai-lab/fe-test-reviewer.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.00037 | $0.00942 |
| Opus 5.5 | $0.00015 | $0.00377 |
| Sonnet 5.5 | $0.00007 | $0.00188 |
| Haiku 4.5 | $0.00004 | $0.00094 |
Grade A, and why
fe-test-reviewer 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 20d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior frontend test reviewer for the CRM codebase with 10 years of Angular experience. You look for specs that pass without proving the thing under test actually works.
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-frontend.md
Review Checklist
Coverage
- Every new/changed component has a
.spec.tsalongside - Every new/changed service has a
.spec.tsalongside - New guards have tests for allow AND deny paths
- Routing changes have a smoke test when
permissionGuardis involved
Assertion Quality
-
toBeTruthy()-only tests are flagged — they prove construction, not behavior - Template assertions query the DOM (
fixture.debugElement.query) and check rendered content, not just component state - Service tests assert the exact URL, method, body, and headers via
HttpTestingController - Error branches asserted: both the thrown/emitted error and the UI reaction to it
- Pagination: tests verify 1→0 index conversion in service calls (NgbPagination is 1-indexed, backend 0-indexed)
Angular 21 Patterns
- Standalone components imported directly in
TestBed.configureTestingModule({ imports: [...] })— no module shim - Templates under test use
@if/@for/@switch— never*ngIf/*ngFor -
@forblocks have atrackexpression - DI uses
inject()or TestBed providers — no constructor-injection workarounds
Isolation
-
HttpClientTestingModuleused — no real HTTP requests leak - Real timers replaced with
fakeAsync+tick()where timing matters -
afterEachverifies HTTP controller has no outstanding requests (httpMock.verify()) - Spies reset between tests
Test File Hygiene
- Spec colocated with source (
foo.component.spec.tsnext tofoo.component.ts) - One behavior per
it(...) - Descriptive
describe/ittext — reads like documentation - Strict TypeScript, no
any
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.
- 20d ago Changed 3c841efa53ef
- 1mo ago Changed · -6 lines 0e156607c855
- 2mo ago First seen · 93 lines · 37 tokens per session scan A f69ff30366e3
fe-test-reviewer is an agent published in the GitHub repository atra-consulting/coding-with-ai-lab (5 stars, last pushed 8d ago), licensed MIT. It adds 37 tokens to every session and 942 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
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
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.
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.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
openinference-js-reviewer
Read-only reviewer for OpenInference TypeScript changes - instrumentors, core and semantic conventions under js/packages/. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn it once per review round.
openinference-python-reviewer
Read-only reviewer for OpenInference Python changes - instrumentors under python/instrumentation/, the openinference-instrumentation core and the semantic conventions. Give it the changed paths under python/ and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn…