agentmods.dev

sdd-status

sdd-status is a command for Claude Code from Gentleman-Programming/gentle-ai. It costs 9 tokens per session (807 once invoked), scanned A, original, MIT.

A read-only command that shows the structured status of an active software change managed through SDD, a process for organizing development work into documented changes.

In plain words
What is it for?
Use it to inspect the status of a named change, including its stored work and progress, after the required session preflight is complete.
Why use it?
It gives a current status view without starting executors or editing project files, but it requires an SDD session setup first.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: agent in frontmatter; mentions OpenCode.

not rated 6.3k +116 changed 3d ago A scan 9 tokens original MIT
View the source file Gentleman-Programming/gentle-ai gentle-ai.gentlemanprogramming.com
About the project

Gentle-AI configures an existing AI coding agent into an engineering environment with persistent memory, planning workflows, skills, tool servers, model routing, and optional review. Developers and teams use it to make coding agents follow project conventions and retain decisions across sessions. The catalogue entries are its skills, commands, agents, and instruction.

Gentleman-Programming/gentle-ai · 6,255 stars · on GitHub · gentle-ai.gentlemanprogramming.com

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/gentleman-programming/gentle-ai/sdd-status
Clone the repo
git clone --depth 1 https://github.com/Gentleman-Programming/gentle-ai

Made for: Claude Code.

Wrote 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.

agentmods badge for sdd-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/gentleman-programming/gentle-ai/sdd-status.svg)](https://agentmods.dev/commands/gentleman-programming/gentle-ai/sdd-status)
Your own site
<a href="https://agentmods.dev/commands/gentleman-programming/gentle-ai/sdd-status"><img src="https://agentmods.dev/badge/commands/gentleman-programming/gentle-ai/sdd-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 807 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.1 $0.00009 $0.00807
Opus 5 $0.00005 $0.00404
Sonnet 5 $0.00002 $0.00161
Haiku 4.5 $0.00001 $0.00081

Measured 3d ago against content hash a81f72cfaa2d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

sdd-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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

internal/assets/opencode/commands/sdd-status.md · 42 lines

What it actually says

You are the gentle-orchestrator. This command is read-only. Do not launch SDD executors and do not edit files.

HARD GATE:

SDD Session Preflight must already be complete for this session. It must include execution mode, artifact store, chained PR strategy, and review budget. If missing, ask the exact orchestrator preflight prompt and STOP. Do not inspect status in the same turn.

CONTEXT:

  • Working directory: before doing anything else, run git rev-parse --show-toplevel 2>/dev/null || pwd with your bash tool and use the returned path as the authoritative workspace.
  • Current project: the basename of the detected workspace above.
  • Change name: $ARGUMENTS

TASK:

  1. If the gentle-ai binary is available, run gentle-ai sdd-status [change] --cwd <repo> --json --instructions and treat its JSON as authoritative — but only when the session artifact store is openspec or hybrid. When the session artifact store is engram, do NOT invoke the native dispatcher at all — it cannot see the change (it reads only openspec/changes/); resolve status entirely from Engram (mem_search + mem_get_observation on the change's topic keys) using the manual status schema in ~/.config/opencode/skills/_shared/sdd-status-contract.md (the same schema used when the binary is unavailable). The dispatcher is authoritative only for openspec/hybrid. If unavailable, read the installed shared status contract from this agent's skills directory and follow it. Use ~/.config/opencode/skills/_shared/sdd-status-contract.md for OpenCode, ~/.config/kilo/skills/_shared/sdd-status-contract.md for Kilo Code, ~/.qwen/skills/_shared/sdd-status-contract.md for Qwen, or the equivalent configured skills directory for the current adapter. Do not use a workspace-relative skills/_shared/... path.
  2. Resolve the active change:
    • If $ARGUMENTS is provided, validate that exact change in the selected artifact store.
    • If omitted and exactly one active change exists, select it and say how it was selected.
    • If omitted or ambiguous with multiple active changes, ask the user to choose and STOP. Do not guess.
  3. Inspect the selected artifact store from session preflight. Do not hardcode Engram.
  4. Return structured status with:
    • Active change selection and schemaName.
    • planningHome, changeRoot, artifactPaths, and contextFiles.
    • Artifact statuses for proposal, specs, design, tasks, apply-progress, and verify-report.
    • Task progress: total, completed, pending, and allComplete.
    • Dependency states for proposal, specs, design, tasks, apply, verify, and archive.
    • Next recommended action.
    • actionContext mode, workspace root, and allowed edit roots.

READ-ONLY RULES:

  • Do not create, update, or delete artifacts.
  • Do not mark tasks complete.
  • Do not launch apply, verify, archive, or continue.
  • Do not infer routing from free text. Use nextRecommended and dependency states. If blockedReasons is non-empty, do not proceed to apply, archive, or terminal work. If nextRecommended is verify, verification/remediation may run only to refresh evidence; if nextRecommended is resolve-blockers, report blockedReasons and stop; if nextRecommended is a planning token (propose, spec, design, or tasks), launch the corresponding planning phase.
  • If status cannot be resolved safely, return status: blocked with the missing information.
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. 3d ago Changed · +1 lines a81f72cfaa2d
  2. 6d ago First seen · 41 lines · 9 tokens per session scan A fdcfab9d3d97

Subscribe to this mod's changes

sdd-status is a command published in the GitHub repository Gentleman-Programming/gentle-ai (6,255 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 807 once invoked, about $0.0000 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.

Planning
Related

Other commands, from other repositories

checklist

Generate a custom checklist for the current feature based on user requirements.

github/spec-kit · 13 tokens

clarify

Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.

github/spec-kit · 27 tokens

specify

Create or update the feature specification from a natural language feature description.

github/spec-kit · 13 tokens

analyze

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

github/spec-kit · 26 tokens

constitution

Create or update the project constitution from interactive or provided principle inputs.

github/spec-kit · 13 tokens

converge

Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.

github/spec-kit · 35 tokens