status

A command that reports the current stage of an AIDD (AI-assisted development) project and the state of its decision gate and saved work.

In plain words
What is it for?
Use it to check project status, identify blockers, find the next command, and review the approved choices that constrain implementation.
Why use it?
It quickly shows what has happened, what is blocking progress, and what should happen next. After approval, it also keeps binding decisions visible.

Command

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/rchase999/aidd/status
Clone the repo
git clone --depth 1 https://github.com/rchase999/aidd
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 121 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.00012 $0.00121
Opus 5 $0.00006 $0.00060
Sonnet 5 $0.00002 $0.00024
Haiku 4.5 $0.00001 $0.00012

Measured 2d ago against content hash c3b689a00110, 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.

aidd/commands/status.md · 13 lines

What it actually says

AIDD Status

!node "${CLAUDE_PLUGIN_ROOT}/scripts/aidd.mjs" status 2>&1 || echo "no .aidd workspace in this directory"

Summarise in three lines: where the run is, what is blocking it, what the single next command is.

If the gate has passed, also name the load-bearing APPLY choices from .aidd/02-research/decisions.md so the constraints stay visible.

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 · 13 lines · 12 tokens per session scan A c3b689a00110

Subscribe to this mod's changes

status is a command published in the GitHub repository rchase999/aidd (2 stars, last pushed 23d ago), licensed MIT. It adds 12 tokens to every session and 121 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-31.