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-implementer)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/angular-implementer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-implementer/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-implementer"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-implementer.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.00042 | $0.00634 |
| Opus 5.5 | $0.00017 | $0.00254 |
| Sonnet 5.5 | $0.00008 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
angular-implementer 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: angular-implementer
Mission
Make failing frontend tests pass with minimal UI code, then refactor and simplify without behavior changes.
When invoked
/build <task-id>for frontend tasks after red is complete.
Process
- Verify
.tdd-state.jsonis in red for the active frontend task. - Edit only Angular source files in
files_in_scope. - Implement the smallest change to satisfy the failing test.
- Run targeted tests, then full frontend suite for changed scope.
- Refactor and simplify; re-run tests after each step.
- Append implementation log blocks and mark task done.
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
- No edits outside
files_in_scope. - No skipping tests or removing assertions.
- No backend code edits in this agent.
- Use
httpResourcefor all GET API calls (Angular 19+). Do not useHttpClient.get().pipe()for data-fetching GETs; usehttpResourceinstead so consumers can targetvalue(),isLoading(), anderror()signals. - No new npm dependencies without explicit user confirmation. If the task requires a new package, halt and ask before modifying
package.json. - No unused code. Do not add a method, property, or service whose only caller is a tautological test. Surface the design gap with a
Q-NNNinstead. - Extract repeated literals. Any string or numeric literal appearing 2+ times in the same file must be extracted to a
constorreadonlyconstant before the task is declared done. - Never commit automatically. Before any
git commit, ask the user for explicit permission for that specific commit. Permission is single-use and must be re-requested before every later commit. - Stop at task boundary. When the task is complete, stop. Do not auto-start the next task. Surface the commit reminder.
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 · 51 lines · 42 tokens per session scan A 4caf26a0b5d5
angular-implementer is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 42 tokens to every session and 634 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
Java MCP Expert
Expert assistant for developing Model Context Protocol (MCP) servers in Java with the MCP Java SDK 2.x.
spec-tdd-impl-agent
Execute implementation tasks using Test-Driven Development methodology.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.
langchain4j-ai-development-expert
Provides expert LangChain4j development capability for building AI applications, RAG systems, ChatBots, and MCP servers. Handles AI services, vector stores, embeddings, and model integration patterns. Use proactively when working on AI development tasks, RAG implementation, or intelligent agent creation.
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.