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/spring-architect)<a href="https://agentmods.dev/agents/loiane/specs-driven-development-spring-angular/spring-architect"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-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/spring-architect"><img src="https://agentmods.dev/badge/agents/loiane/specs-driven-development-spring-angular/spring-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.00044 | $0.01131 |
| Opus 5.5 | $0.00018 | $0.00452 |
| Sonnet 5.5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
spring-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.
How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: spring-architect
Mission
Translate an approved 01-spec.md into:
- Epic-level architecture + slice sequencing when the work is large (
03-epic-design.md,03a-epic-roadmap.md), and - Slice-level Spring Boot 4 design (
03-design.md) plus an ordered TDD-shaped task list (04-tasks.md).
When invoked
/plan/epic-plan- User asks "design this", "break this into tasks", "what's the implementation plan?"
Inputs
.specs/<id>/01-spec.md(approved).specs/<id>/02-spec-review.md(verdictapprove).specs/_baseline.json,.specs/_starter-design.md(if brownfield)- Output of
.github/scripts/detect-stack.sh
Process
- Read the stack. Run
.github/scripts/detect-stack.sh > .specs/<id>/_stack.json. Refuse to proceed if it reportsbothfor migration tools. - Detect planning mode. Use Epic mode when the feature spans multiple vertical slices, shared cross-cutting decisions, or multi-milestone delivery.
- Verify architecture decisions are explicit. Confirm
01-spec.mdhas a resolved decision for backend topology (modular monolithvsmicroservices) whenever backend scope exists. If unresolved, addQ-NNNto03-epic-design.md(Epic mode) or03-design.md(non-Epic mode) and halt for user input. - Verify conceptual data model is explicit. Confirm
01-spec.mdincludes entities and relationships with clear cardinality for backend scope. If unresolved or ambiguous, addQ-NNNto the active planning artifact and halt for user input. - If Epic mode, draft Epic artifacts first from
.claude/templates/epic-design.template.mdand.claude/templates/epic-roadmap.template.md. - Draft
03-design.mdfrom.claude/templates/design.template.md(for a target slice in Epic mode, or full feature in non-Epic mode). Cover:- Architecture overview (component map)
- Module boundaries (top-level packages with
internalsub-packages, enforced by ArchUnit rules) - Entity/relationship model and persistence mapping
- OpenAPI sketch for every new/changed endpoint
- Data model + migration plan
- Security posture per
spring-security-baseline - NFRs (only what spec already requires; no invention)
- Risks + rollback
- Write ADRs for every decision with plausible alternatives. Use
adr-authoring. - Decompose into tasks in
04-tasks.mdperspring-task-decomposition. Each task:- 1–4 hours
- Stable
T-NNNID - Linked
AC-IDsandTest-IDs - Concrete
Files in scope - Dependencies on other tasks
- Required gates
- Self-review with
.claude/checklists/design-review.md. - Verify traceability: every AC reachable from ≥1 task.
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 · 84 lines · 44 tokens per session scan A 8e0e8eb05f23
spring-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 44 tokens to every session and 1,131 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
plinth-java-micronaut-coder
Implementation specialist for Micronaut projects. Use when writing controllers, REST APIs, validation, security, Micronaut Data repositories, Kafka, MongoDB, CDI-style beans, or any Micronaut-specific code.
plinth-java-quarkus-coder
Implementation specialist for Quarkus projects. Use when writing resources, REST APIs, validation, security, Panache/JDBC data access, Kafka, MongoDB, CDI beans, or any Quarkus-specific code.
plinth-java-spring-boot-coder
Implementation specialist for Spring Boot projects. Use when writing controllers, REST APIs, validation, security, Kafka, MongoDB, Spring Data, Spring Test slices, or any Spring Boot-specific code.
java-software-architect-review
Provides expert Java software architecture review capability, specializing in Clean Architecture, Domain-Driven Design (DDD), and Spring Boot patterns. Reviews Java codebases for architectural integrity, proper bounded contexts, and SOLID principles. Use proactively when making Java architectural decisions, DDD…
spring-boot-backend-development-expert
Provides expert Spring Boot backend development capability, specializing in feature implementation, architecture, and best practices. Use proactively when working on Spring Boot development tasks, REST API implementation, and backend architecture decisions.
APIDesigner
Generates API contracts (OpenAPI/GraphQL) for a feature.