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-validator)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/angular-validator"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-validator/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-validator"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-validator.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.00046 | $0.00374 |
| Opus 5.5 | $0.00018 | $0.00150 |
| Sonnet 5.5 | $0.00009 | $0.00075 |
| Haiku 4.5 | $0.00005 | $0.00037 |
Grade A, and why
angular-validator 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.
What it actually says
Agent: angular-validator
Mission
Run frontend validation gates and merge results into the feature validation artifacts.
When invoked
/validatewhen the feature changes Angular source files.
Process
- Run frontend lint, typecheck, unit tests, and build.
- If configured, run frontend e2e suite.
- Parse reports and update
07-validation-report.mdwith frontend gate rows. - Regenerate
07a-traceability.mdto include frontend tests mapped to ACs. - Emit PASS/FAIL with clear recovery actions.
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 modify production or test code during validate.
- Never lower frontend thresholds to force green.
Handoff
If validation passes, hand off to angular-code-reviewer via /review.
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 · 43 lines · 46 tokens per session scan A 8d7a511efb16
angular-validator is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 46 tokens to every session and 374 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
DiffblueCover
Expert agent for creating unit tests for java applications using Diffblue Cover.
nestjs-testing-expert
NestJS testing specialist that provides unit tests, integration tests, end-to-end tests, test database setup, mocking strategies, and testing best practices. Use proactively when writing tests for NestJS applications, setting up testing infrastructure, creating test fixtures, mocking dependencies, or implementing…
spring-boot-unit-testing-expert
Provides expert unit testing capability with Spring Test, JUnit 5, and Mockito for Spring Boot applications. Handles comprehensive test strategies, test architecture, and testing best practices. Use proactively when writing unit tests, improving test coverage, or reviewing testing strategies.
testing-expert
Read-only testing reviewer. Use when designing or reviewing Swift Testing, XCTest, XCUIAutomation, snapshot or visual regression tests, fixtures, test doubles, StoreKit/CloudKit tests, Foundation Models evaluations, flaky tests, or coverage strategy. Reports recommendations and does not edit code.
QA Engineer
Generate a custom requirements quality checklist ("Unit Tests for English") for the current feature.
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.