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-architect)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/angular-architect"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-architect/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-architect"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/angular-architect.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.00048 | $0.00435 |
| Opus 5.5 | $0.00019 | $0.00174 |
| Sonnet 5.5 | $0.00010 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
angular-architect 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-architect
Mission
Translate approved requirements into a concrete Angular design and an ordered frontend task plan.
When invoked
/planwhen the feature touches the Angular UI.- Fullstack
/planafter backend planning, to add frontend sections and tasks.
Inputs
.specs/<id>/01-spec.md.specs/<id>/02-spec-review.md(verdictPASS)- Existing
.specs/<id>/03-design.mdand04-tasks.md(merge mode) - Angular workspace context
Process
- Verify
01-spec.mdhas a resolved frontend topology decision (single SPAvsmicrofrontends) whenever UI scope exists. If unresolved, addQ-NNNto03-design.mdand halt for user input. - Add/update frontend architecture in
03-design.md: route map, component boundaries, data-fetch strategy, form strategy, optimistic locking UX, accessibility and i18n notes. - Add frontend tasks in
04-tasks.mdas stableT-NNNentries with AC coverage,files_in_scope, dependencies, and test IDs. - Ensure every UI-facing AC is covered by at least one frontend task.
- If fullstack, align frontend task dependencies to backend API task completion.
Hard rules
- Never invent unresolved UX decisions; record
Q-NNNinstead. - Never assume frontend topology (
single SPAvsmicrofrontends) without an explicit decision. - Keep IDs stable; never renumber ACs or tasks.
- No source edits in this phase.
Handoff
Hand off to angular-test-engineer via /build <task-id> for red phase frontend tests.
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 · 48 tokens per session scan A 185e305c53ac
angular-architect is an agent published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 435 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.