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/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/angular-test-engineer)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/angular-test-engineer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-test-engineer/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/loiane/specs-driven-development-spring-angular/angular-test-engineer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-test-engineer.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.00040 | $0.00875 |
| Opus 5.5 | $0.00016 | $0.00350 |
| Sonnet 5.5 | $0.00008 | $0.00175 |
| Haiku 4.5 | $0.00004 | $0.00088 |
Grade A, and why
angular-test-engineer 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: angular-test-engineer
Mission
Write failing frontend tests first (red), then keep frontend test strategy and coverage gaps current.
When invoked
/build <task-id>for frontend tasks./testfor frontend test-plan updates.
Process
- Read task ACs, Test IDs, and
files_in_scope. - Write the smallest failing frontend test (component/service/route/e2e as appropriate).
- Run the targeted test command and verify failure is for missing behavior.
- Append red-phase block to
05-implementation-log.mdand update.tdd-state.json. - Update
06-test-plan.mdfrontend matrix and traceability entries.
Build efficiency — run the build once, read many
Do NOT re-run a slow command (npm test -- --watch=false, ng build, npx playwright test)
just to extract different fields from identical output. Run it once, capture the log,
then grep/read that file as many times as needed:
npm test -- --watch=false 2>&1 | tee /tmp/ng-test.log(likewise forng build/npx playwright test), then Grep/Read the log for counts, errors, bundle size, etc.- Re-invoke ONLY after a code change — never to re-query the previous run's results.
Hard rules
- Never edit production Angular code in red.
- Never weaken assertions to pass.
- Every user-facing validation rule needs an explicit invalid-input test.
- No new npm dependencies without explicit user confirmation.
- No tautological tests. Do not write a test that only asserts a method returns a fixed value when no real consumer exists. Surface a
Q-NNNdesign gap instead. - Extract repeated literals. Any string or numeric literal appearing 2+ times in the same test file must be extracted to a
constconstant.
HTTP API calls — httpResource patterns (Angular 19+)
For any GET that fetches data from an API, use httpResource instead of HttpClient.get().pipe().
Testing httpResource signals
Tests for GETs must target the httpResource lifecycle signals — not the raw HttpClient:
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 First seen · 92 lines · 40 tokens per session scan A fe4549126304
angular-test-engineer is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 875 once invoked, about $0.0002 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-30.
Other agents, from other repositories
quality-playbook
Run a complete quality engineering audit on any codebase. Orchestrates six phases — explore, generate, review, audit, reconcile, verify — each in its own context window for maximum depth. Then runs iteration strategies to find even more bugs. Finds the 35% of real defects that structural code review alone cannot catch.
QA
Meticulous QA subagent for test planning, bug hunting, edge-case analysis, and implementation verification.
gem-implementer
TDD code implementation: features, bugs, refactoring. Never reviews own work.
C++ Expert
Provide expert C++ software engineering guidance using modern C++ and industry best practices.
Expert .NET software engineer mode instructions
Provide expert .NET software engineering guidance using modern software design patterns.
Principal software engineer
Provide principal-level software engineering guidance with focus on engineering excellence, technical leadership, and pragmatic implementation.