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/status)<a href="https://agentmods.dev/commands/loiane/specs-driven-development-spring-angular/status"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/status/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/status"><img src="https://agentmods.dev/badge/commands/loiane/specs-driven-development-spring-angular/status.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.00335 |
| Opus 5.5 | $0.00007 | $0.00134 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
status 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
/status
Phase: meta — read-only Owning agent: none (pure reporting)
Purpose
Show the user where every active feature stands. No writes, no side effects.
Inputs
- Optional
<feature-id>; without it, summarize all features under.specs/.
Reads
.specs/*/01-spec.md,02-spec-review.md,03-epic-design.md,03a-epic-roadmap.md,03-design.md,04-tasks.md,.tdd-state.json,07-validation-report.md.target/harness-summary.jsonif present.
Writes
Nothing.
Process
For each feature (or the supplied one), produce a one-row-per-feature table:
feature_idphase— derived from which artifacts exist + verdicts (specify, spec-review, plan-epic, plan, build, test, validate, review, done).acs_total,acs_with_teststasks_done / tasks_totallast_validate_verdictand timestampactive_taskfrom.tdd-state.json(if any) and its currentphase
Then print a single sentence: "Recommended next action: …".
Refuse if
Never. This command never refuses; if data is missing it shows —.
Done when
Status table is printed and a recommended next command is suggested.
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 · 40 lines · 17 tokens per session scan A 4bcc0f8faa2e
status is a command published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 8d ago), licensed MIT. It adds 17 tokens to every session and 335 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-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.
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-tasks
Command description: Generate an actionable task list from the current plan. Argument hint: [optional: feature directory or task focus] Command category: feature-delivery Prerequisites: spec, plan.