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-db-reverse-full.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-db-reverse-full)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-db-reverse-full"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-db-reverse-full/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-db-reverse-full"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-db-reverse-full.svg" alt="Reviewed on agentmods" width="80" 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.00133 | $0.07243 |
| Opus 5.5 | $0.00053 | $0.02897 |
| Sonnet 5.5 | $0.00027 | $0.01449 |
| Haiku 4.5 | $0.00013 | $0.00724 |
Grade A, and why
sdd-db-reverse-full 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 1mo 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdd-db-reverse-full [--project DB] [--max-parallel N] [--sequential] [--no-architect] [--json]
Rôle
Orchestrateur du reverse engineering base de données → FEATs. À partir de la
connexion déclarée dans stack.md ## Active Database, il lit toutes les
procédures stockées en lecture seule, les regroupe en modules métier, et
produit des FEATs SDD_Pro standard consommables par /sdd-full.
stack.md (## Active Database) ← config + variables d'environnement (${VAR} via .env)
└─[Phase 1 introspect READ-ONLY]─► proc-snapshot/*.sql + db-introspection.json
│ + schema-snapshot/*.sql + db-schema.json + inventory.json
└─[Phase 0.A déterministe]─► FAITS : CRUD, graphe d'appels, plan de vagues
└─[Phase 0.B reverse-db-architect]─► HYPOTHÈSES : glossaire, domaines, risques
└─► db-context.json (SSoT versionné) + db-context/packs/{objet}.md
└─[vagues : feuilles d'abord, spécialistes en parallèle borné]
│ proc-analyst · function-analyst · view-analyst · trigger-analyst
│ └─► us/{n}-{m}-{Name}.md (1 objet SQL = 1 US)
│ └─ résumé réinjecté dans db-context.findings ─┐
│ (barrière de vague, puis vague suivante) ◄─┘
└─[rung 2 : synthèse module]─► feats/{n}-{Module}.md (1 module = 1 FEAT)
└─ validate_reverse_feat + check_reverse_feat_for_full
└─► REVERSE-GATE ─► /sdd-full
Modèle (confirmé)
- 1 objet SQL = 1 User Story · 1 module = 1 FEAT (objets d'un même objet métier).
- Comprendre avant d'écrire : aucune User Story n'est produite avant que la Phase 0 ait construit le Database Context. Un analyste ne redécouvre jamais la base — il reçoit le slice qui le concerne.
- Remontée stricte : la FEAT est composée depuis les US + l'inventaire, jamais en
relisant le corps SQL. L'assembleur lit réellement les US (titre métier, ACs,
mode d'extraction) et y écrit en retour
Covers:+ leParent FEAT hash. - Faits ≠ hypothèses : les faits viennent des scripts déterministes et peuvent devenir des Acceptance Criteria ; les hypothèses viennent de l'architecte et ne le peuvent jamais. La séparation est structurelle.
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.
- 1mo ago First seen · 405 lines · 133 tokens per session scan A a44a84949620
sdd-db-reverse-full is a command published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 133 tokens to every session and 7,243 once invoked, about $0.0005 per session on Opus 5.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.
Other commands, from other repositories
init
Initialize configurations for Supabase local development.
security
Scan a SQL string, .sql file, or SQL-building source file for injection risks with GoSQLX.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
new-migration
Scaffold a new database migration file pair (up + down) with auto-detection of migration tool and numbering.
json.batch_get
Read multiple JSON values by document and path.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.