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/commands/loiane/specs-driven-development-spring-angular/build)<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/build"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/build/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/commands/loiane/specs-driven-development-spring-angular/build"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/build.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.00017 | $0.01095 |
| Opus 5.5 | $0.00007 | $0.00438 |
| Sonnet 5.5 | $0.00003 | $0.00219 |
| Haiku 4.5 | $0.00002 | $0.00110 |
Grade A, and why
build 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build
Phase: 4 — build (TDD)
Owning agent: .claude/agents/spring-implementer.md (collaborates with spring-test-engineer)
Skills used: tdd-red-green-refactor, spring-boot-4-conventions, clarity-over-cleverness, junit5-testcontainers-patterns, spring-task-decomposition
Stack routing
| Task type | Red step agent | Green/refactor/simplify agent |
|---|---|---|
Backend (src/main/java/**, src/test/java/**) |
spring-test-engineer |
spring-implementer (this agent) |
Frontend (src/**/*.ts, src/**/*.html, src/**/*.scss) |
angular-test-engineer |
angular-implementer |
Determine the task type from its files_in_scope in 04-tasks.md. If all files are frontend paths, delegate to the Angular agents. If mixed, split into sub-steps: backend first (Spring agents), then frontend (Angular agents).
Purpose
Execute one task end-to-end through the four TDD phases (red → green → refactor → simplify), updating .tdd-state.json and appending a block to 05-implementation-log.md after each phase.
Inputs
<task-id>(e.g.T-001). Required.
Reads
.specs/<feature-id>/04-tasks.md.specs/<feature-id>/03-design.md.specs/<feature-id>/.tdd-state.json.claude/skills/tdd-red-green-refactor/SKILL.md(authoritative)
Writes
src/test/**andsrc/main/**files listed intasks[<task-id>].files_in_scope..specs/<feature-id>/.tdd-state.json(phase transitions)..specs/<feature-id>/05-implementation-log.md(one### <task-id> — <phase>block per phase).
Process
For the supplied <task-id>:
- Pre-flight commit check. Run
git status. If there are uncommitted changes from any prior task, refuse to start. List the changed files and remind:git commit → /build <task-id>. - Activate. Set
.tdd-state.jsonactive_task = <task-id>. Refuse if any other task isphase: red|green|refactor|simplify(one task in flight at a time). - Red. Write the smallest test that captures the next AC slice. Run it. Capture the failure message into
tasks[<task-id>].red_failure_excerpt. Setphase: "red". Append log block. - Green. Write the minimum production code under
files_in_scopeto pass the test. Run only the new test, then run all tests. Setphase: "green". Append log block. - Refactor. Improve structure without changing behavior. Re-run all tests. Set
phase: "refactor". Append log block. - Simplify. Apply
clarity-over-cleverness(untangle ternaries, inline once-used helpers, kill dead options, name domain concepts, extract repeated literals). Re-run all tests. Setphase: "simplify". Append log block. - Done. Set
phase: "done", clearactive_task. If more ACs in this task remain uncovered, immediately re-run from step 2 with the next slice (do not declare done early). - STOP — commit reminder. Surface: files changed (
git status), tests passing, suggested commit message. Recommend:git status → git commit → /build <next-task-id>. Do not auto-start the next task unless the user explicitly requests chaining.
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 · 61 lines · 17 tokens per session scan A b1ad88041ee3
build is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 3d ago), licensed MIT. It adds 17 tokens to every session and 1,095 once invoked, about $0.0001 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 commands, from other repositories
spec-impl
Execute spec tasks using TDD methodology.
kiro-spec-impl
Command "kiro-spec-impl" from gotalab/cc-sdd, covering implementation task executor, core task, execution steps, step 1: load context and step 2: select tasks.
benchmark
Design and coordinate a reproducible Java performance test.
devkit.java.write-integration-tests
Generates comprehensive integration tests for Spring Boot classes using Testcontainers (PostgreSQL, Redis, MongoDB) with @ServiceConnection pattern. Use when writing integration tests for service or repository classes.
devkit.java.write-unit-tests
Generates comprehensive JUnit 5 unit tests for Java classes with Mockito mocking and AssertJ assertions. Use when writing unit tests for service, controller, or utility classes.
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.