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.
npx agentmods add commands/loiane/specs-driven-development-spring-angular/testgit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWhat 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 | $0.00017 | $0.00511 |
| Opus 5 | $0.00009 | $0.00255 |
| Sonnet 5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
test 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 yesterday.
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
/test
Phase: 4 (meta) — test plan + targeted test authoring
Owning agent: .claude/agents/spring-test-engineer.md
Skills used: junit5-testcontainers-patterns, requirements-traceability, pit-mutation-tuning, archunit-rules
Purpose
Author or extend 06-test-plan.md and add tests that close coverage or mutation gaps without doing production work.
Inputs
<feature-id>(positional). Optional--gapflag to read the latesttarget/harness-summary.jsonand target uncovered lines / surviving mutants.
Reads
01-spec.md,03-design.md,04-tasks.md.target/harness-summary.json,target/site/jacoco/jacoco.xml,target/pit-reports/mutations.xml(if present)..claude/templates/test-plan.template.md.
Writes
.specs/<feature-id>/06-test-plan.md.- New or extended files under
src/test/**only. Never modifiessrc/main/**.
Process
- Build/refresh
06-test-plan.md: matrix of AC × test type (unit, slice, integration, contract, mutation-targeted), plus Testcontainers requirements. - If
--gapwas passed, readharness-summary.jsonand JaCoCo/PIT reports; list uncovered lines and surviving mutants asGap-NNNwith proposed tests. - Write the proposed tests with
@Tag("AC-NNN")and descriptive@DisplayName("AC-NNN: ..."). - Run
mvn test(ormvn verifyif integration tests changed) and quote the result tail. - Update the traceability matrix by running
.github/scripts/traceability.sh <feature-id>.
Refuse if
- Asked to modify any file under
src/main/**(delegate to/build). - The active feature has no
04-tasks.md.
Done when
06-test-plan.mdis up to date.- Any
Gap-NNNitems have either a closing test or an explicitWon't fixrationale. - Traceability matrix is regenerated.
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.
- yesterday First seen · 42 lines · 17 tokens per session scan A 26228f9d5f0a
test is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (57 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 511 once invoked, about $0.0001 per session on Opus 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
devkit.refactor
Provides guided code refactoring capability with deep codebase understanding, compatibility options, and comprehensive verification. Use when restructuring or improving existing code.
spec-kitty.analyze
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
devkit.verify-skill
Validates a skill against DevKit standards (requirements, template, dependencies). Use when you need to verify a skill before publishing or after modifications.
devkit.prompt-optimize
Provides expert prompt optimization using advanced techniques (CoT, few-shot, constitutional AI) for LLM performance enhancement. Use when you need to improve prompt quality or optimize LLM interactions.
sdd-plan
Turn a spec into a persisted baby-step plan file — research, resume, impact analysis.
sdd-architecture-update
Detect architecture drift and sync the snapshot + Memory Bank (with confirmation).