status

A read-only command that reports the status of features managed through specification files. It shows phases, test and task progress, validation results, and any active task when that information exists.

In plain words
What is it for?
Use it to check all features or one feature, review completed versus total tasks, inspect the latest validation result, and get a recommended next command.
Why use it?
It gives developers one place to see which features are being specified, planned, built, tested, or validated without changing project files.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/loiane/specs-driven-development-spring-angular/status
Clone the repo
git clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angular

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 335 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00017 $0.00335
Opus 5 $0.00009 $0.00168
Sonnet 5 $0.00003 $0.00067
Haiku 4.5 $0.00002 $0.00034

Measured 2d ago against content hash 4bcc0f8faa2e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/commands/status.md · 40 lines

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.json if present.

Writes

Nothing.

Process

For each feature (or the supplied one), produce a one-row-per-feature table:

  • feature_id
  • phase — derived from which artifacts exist + verdicts (specify, spec-review, plan-epic, plan, build, test, validate, review, done).
  • acs_total, acs_with_tests
  • tasks_done / tasks_total
  • last_validate_verdict and timestamp
  • active_task from .tdd-state.json (if any) and its current phase

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.

Changes

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.

  1. 2d ago First seen · 40 lines · 17 tokens per session scan A 4bcc0f8faa2e

Subscribe to this mod's changes

status 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 335 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.