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/epic-plan)<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/epic-plan"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/epic-plan/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/epic-plan"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/epic-plan.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.00022 | $0.00453 |
| Opus 5.5 | $0.00009 | $0.00181 |
| Sonnet 5.5 | $0.00004 | $0.00091 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
epic-plan 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
/epic-plan
Phase: 3a — Epic planning
Owning agent: .claude/agents/spring-architect.md
Skills used: epic-slicing-planning, spring-boot-4-conventions, openapi-contract-first, adr-authoring, performance-optimization
Purpose
Create high-level Epic planning artifacts before detailed slice-level tasks.
Inputs
<feature-id>.
Reads
.specs/<feature-id>/01-spec.md.specs/<feature-id>/02-spec-review.md(verdict must bePASS).specs/_stack.json.claude/templates/epic-design.template.md.claude/templates/epic-roadmap.template.md
Writes
.specs/<feature-id>/03-epic-design.md.specs/<feature-id>/03a-epic-roadmap.md.specs/<feature-id>/adr/NNN-*.md(if needed)
Process
- Refuse if spec review is not
PASS. - Refuse if
01-spec.mdhas unresolvedQ-NNN. - Produce
03-epic-design.md: boundaries, shared architecture decisions, integration points, risks, and ADR links. - Produce
03a-epic-roadmap.md: vertical slices, dependency order, milestone intent, and rollout strategy. - Raise
Q-NNNfor any unresolved Epic-level decision and halt before detailed task decomposition.
Refuse if
02-spec-review.mdverdict is notPASS.- Any AC in
01-spec.mdis unaccounted for in Epic design/roadmap. - Epic-level
Q-NNNremains unresolved at handoff.
Done when
03-epic-design.md and 03a-epic-roadmap.md exist, are internally consistent, and the next recommended command is /plan.
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 · 44 lines · 22 tokens per session scan A 36c99975fda6
epic-plan is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 5d ago), licensed MIT. It adds 22 tokens to every session and 453 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
onboarding
Establish repository guidance and one unambiguous OpenSpec project before issue work.
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.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.
sddp-analyze
Command description: Audit spec, plan, and tasks for consistency and quality. Argument hint: [optional: analysis focus or remediation request] Command category: feature-delivery Prerequisites: spec, plan, tasks.
sddp-clarify
Command description: Reduce ambiguity in the current feature specification. Argument hint: [optional: ambiguity focus or feature directory] Command category: feature-delivery Prerequisites: spec.