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.
curl -O https://raw.githubusercontent.com/zekiriabd/SDD-Pro/main/.claude/commands/sdd-reverse.mdgit clone --depth 1 https://github.com/zekiriabd/SDD-ProWrote 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/zekiriabd/sdd-pro/sdd-reverse)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse.svg" alt="Measured on agentmods" 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.00103 | $0.01201 |
| Opus 5 | $0.00051 | $0.00600 |
| Sonnet 5 | $0.00021 | $0.00240 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
sdd-reverse 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-reverse {U-N} [--json]
Rôle
Lancer la Phase 3 complète sur une unité : l'escalier ascendant qui
remonte le code legacy jusqu'à une FEAT métier. /sdd-reverse est un séquenceur
de commandes (no-spawn §9 rules/reverse-engineering.md) — il n'invoque aucun
agent directement, il enchaîne les 3 sous-commandes barreau par barreau :
/sdd-reverse {U-N}
├─ 3a /sdd-reverse-analyze {U-N} → plans/{n}-{FeatName}.analysis.md (reverse-tech-analyst)
├─ 3b /sdd-reverse-stories {U-N} → us/{n}-{m}-{Name}.md (reverse-us-writer)
└─ 3c /sdd-reverse-feat {U-N} → feats/{n}-{FeatName}.md (reverse-feat-composer)
Décommission (ADR reverse-spec-ladder D2) : l'ancien
/sdd-reversemono-saut (agentreverse-functional-extractor, code→FEAT en un coup) est remplacé par cet escalier. Le saut unique faisait baver l'altitude technique dans la FEAT métier — l'escalier sépare l'analyse fidèle (3a) de la remontée métier (3b/3c). En mode pré-alloué (L5), plusieurs/sdd-reverse {U-N}peuvent tourner en parallèle borné (§8.2).
Args
| Arg | Type | Description |
|---|---|---|
{U-N} |
string requis | Identifiant U-N stable (ex. U-3) |
--json |
flag | Propagé aux 3 sous-commandes (rapports JSON) |
Pré-conditions
Identiques à /sdd-reverse-analyze (3a — premier barreau possède l'allocation) :
inventory.json passe gate ADV-23, units[id={U-N}] existe, templates présents.
Sinon → ERROR remontée par le barreau concerné ([REVERSE_*]).
Actions (séquence — STOP au premier barreau en échec)
- 3a : exécuter
/sdd-reverse-analyze {U-N}. Échec ([REVERSE_*]) → STOP (pas de 3b/3c). - 3b : exécuter
/sdd-reverse-stories {U-N}. Échec → STOP (pas de 3c). - 3c : exécuter
/sdd-reverse-feat {U-N}. - Émission ligne chat finale
[REVERSE] {U-N} → escalier 3a→3b→3c terminé, FEAT {n}-{FeatName} (confidence={cap}). (PROGRESS%).
Sortie
workspace/plans/{n}-{FeatName}.analysis.md (3a — analyse technique legacy)
workspace/us/{n}-{m}-{Name}.md (3b — user stories)
workspace/feats/{n}-{FeatName}.md (3c — FEAT métier, pont vers /sdd-full)
workspace/old/{P}/.sys/modules/{FeatName}/{extraction,stories-3b,feat-3c}.md (logs)
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.
- 3d ago First seen · 78 lines · 103 tokens per session scan A c6b5bda3cce0
sdd-reverse is a command published in the GitHub repository zekiriabd/SDD-Pro (191 stars, last pushed 4d ago), licensed Apache-2.0. It adds 103 tokens to every session and 1,201 once invoked, about $0.0005 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.