SDD-Pro: Command for Claude Code

.claude/commands/sdd-reverse-status.md

sdd-reverse-status is a command for Claude Code from zekiriabd/SDD-Pro. It costs 73 tokens per session (867 once invoked), scanned A, original, Apache-2.0.

A read-only diagnostic command that reports the progress of reverse-engineering projects and extracted feature documents. It shows which stages have been completed and the confidence attached to reverse-engineered features.

In plain words
What is it for?
Use it to check all legacy projects or filter the report to one project. The result can be displayed for people or emitted as machine-readable JSON.
Why use it?
It removes the need to inspect project folders and files manually to understand progress. It also highlights whether a reverse-engineered feature is allowed to continue through the rebuild workflow.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is zekiriabd/SDD-Pro's own configuration. It tells Claude Code how to work on SDD-Pro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything SDD-Pro configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python .sdd/python/sdd_reverse_scripts/reverse_status.py [--project ...] [--json].

Reuse

Borrowing it

Nothing to install: this file belongs to zekiriabd/SDD-Pro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zekiriabd/SDD-Pro/main/.claude/commands/sdd-reverse-status.md
Clone the repo
git clone --depth 1 https://github.com/zekiriabd/SDD-Pro

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-reverse-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-status.svg)](https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-status)
Your own site
<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-status"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 867 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.00073 $0.00867
Opus 5 $0.00036 $0.00434
Sonnet 5 $0.00015 $0.00173
Haiku 4.5 $0.00007 $0.00087

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

Security

Grade A, and why

sdd-reverse-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.

.claude/commands/sdd-reverse-status.md · 88 lines

How it starts

The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/sdd-reverse-status [--project {LegacyProject}] [--json]

Rôle

Diagnostic read-only du workflow reverse engineering. Pendant du /sdd-status SDD_Pro standard, scoped reverse.

Args

Arg Type Description
--project {LegacyProject} optionnel Filtre sur un projet spécifique. Par défaut : tous les projets sous workspace/old/
--json flag Sortie JSON machine-readable

Actions

Invoque le script déterministe (aucun agent) :

python .sdd/python/sdd_reverse_scripts/reverse_status.py [--project ...] [--json]

Le script :

  1. Liste tous les sous-dossiers de workspace/old/ (sauf .)
  2. Pour chacun, détecte la phase atteinte :
    • init : .sys/ existe
    • inventory : .sys/inventory.json existe
    • audit : .sys/tech-audit.md existe
    • db_merged : .sys/db-schema.merged.json existe
  3. Calcule pour chaque projet : feats_extracted / units_total (depuis _featAllocations vs units[])
  4. Liste les FEATs generated-by: sdd-reverse dans workspace/feats/ avec :
    • Marker [REV] (confidence=high) ou [REV⚠️] (medium/low)
    • allow_sdd_full depuis le commentaire <!-- REVERSE-GATE -->
    • source-unit, confidence, language-detected

Sortie humaine

═══ Reverse Engineering Status ═══

Projets legacy : 2

  • HelloWebForms
      init✓ → inventory✓ → audit✓ → merged✓
      FEATs : 2/2 unités extraites (100%)

  • LegacyJava
      init✓ → inventory✓ → audit✗ → merged✗
      FEATs : 1/5 unités extraites (20%)


FEATs reverse dans workspace/feats/ : 3

  [REV] 1-Login  (confidence=high, U=U-1)
        → /sdd-full OK
  [REV⚠️] 2-Home  (confidence=medium, U=U-2)
        → REVUE HUMAINE OBLIGATOIRE avant /sdd-full
  [REV⚠️] 3-Dashboard  (confidence=low, U=U-3)
        → REVUE HUMAINE OBLIGATOIRE avant /sdd-full

Sortie JSON

{
  "ok": true,
  "projects": [
    {"name": "HelloWebForms", "phases": {...}, "units_total": 2, "feats_extracted": 2, ...},
    ...
  ],
  "feats": [
    {"file": "...", "name": "1-Login", "confidence": "high", "marker": "[REV]", "allow_sdd_full": true, ...},
    ...
  ]
}

Read the full file on GitHub · 88 lines

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 First seen · 88 lines · 73 tokens per session scan A f5a2bc36dcc2

Subscribe to this mod's changes

sdd-reverse-status is a command published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 73 tokens to every session and 867 once invoked, about $0.0004 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-09-03.