What is sdd-reverse-synth?

A read-only command that creates system-level documentation from existing project inventories, dependency data, and database schema data. C4 diagrams describe system structure, an ERD describes database relationships, and a summary document explains the system for readers.

Use it to generate C4 architecture diagrams, a complete entity-relationship diagram, and an executive system summary. You can choose the detail level or regenerate only selected documents.

It provides an overview of the whole legacy project when feature-by-feature analysis is not enough. Its output stays separate from feature specifications so it does not get treated as implementation work.

How zekiriabd/SDD-Pro configures Claude Code

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-synth/github.svg)](https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-synth)

Your own site

<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-synth"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-synth/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-reverse-synth"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-reverse-synth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 114 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,439 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.

Model	Per session	Once invoked
Fable 5.1	$0.00114	$0.01439
Opus 5.5	$0.00046	$0.00576
Sonnet 5.5	$0.00023	$0.00288
Haiku 4.5	$0.00011	$0.00144

Measured 1mo ago against content hash fc45ea51b1ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/sdd-reverse-synth.md · 95 lines

How it starts

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

/sdd-reverse-synth {LegacyProject} [--doc-level essentiel|complet|detaille] [--only c4,erd,soul] [--json]

Rôle

Produire la vue système que l'escalier 3a→3b→3c ne produit pas : diagrammes C4, ERD complet et soul.md (synthèse exécutive). C'est un nouvel étage au-dessus de 3c : un consommateur en lecture seule des artefacts déterministes déjà présents, qui ne touche ni à l'escalier, ni au contrat FEAT.

Pare-feu (non-cassant) : tous les artefacts sont écrits sous workspace/old/{P}/.sys/synthesis/ — jamais sous workspace/feats/. /sdd-full ne voit donc jamais un C4/ERD comme une FEAT à coder.

Args

Arg	Type	Description
`{LegacyProject}`	string requis	Sous-dossier de `workspace/old/`
`--doc-level`	`essentiel\|complet\|detaille` (défaut `complet`)	Bouton d'économie de contexte. `essentiel` = C4-contexte + ERD + soul. `complet` = + C4 conteneurs/composants. `detaille` = + table de détail par composant.
`--only`	liste parmi `c4,erd,soul`	Régénère seulement les catégories listées (les autres ne sont pas touchées)
`--json`	flag	Rapport JSON sur stdout

Pré-conditions

workspace/old/{P}/.sys/inventory.json présent et schemaVersion == 1 (sinon → STOP [REVERSE_NO_SOURCE] / [REVERSE_INVENTORY_SCHEMA_STALE]).
Recommandé : /sdd-reverse-audit exécuté avant (produit deps-graph.json → C4 plus riche, et db-schema.merged.json → ERD enrichi). Dégradation gracieuse si absents : le C4 se limite au contexte, l'ERD à la base.

Actions (no-spawn — script déterministe)

Invoque le script déterministe, aucun agent :

python .sdd/python/sdd_reverse_scripts/reverse_synth.py --project workspace/old/{LegacyProject} [--doc-level ...] [--only ...] [--json]

Le script :

Charge inventory.json (requis), deps-graph.json et db-schema.merged.json (ou db-schema.json) si présents.
Nettoie les sorties gérées de chaque catégorie régénérée (idempotence : repasser à un --doc-level inférieur n'y laisse pas d'artefact périmé).
Rend, sous .sys/synthesis/, selon le doc-level : c4-context.md, c4-containers.md, c4-components.md, erd-complete.md, soul.md.
Écrit manifest.json (enregistrement d'observabilité dérivé — quels artefacts, depuis quelles sources, répartition de confiance).
Émet la ligne chat finale : [REVERSE] Synthèse ({doc-level}) : {fichiers} [confiance high=.. medium=.. low=..]. (100%)

Read the full file on GitHub · 95 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.

1mo ago First seen · 95 lines · 114 tokens per session scan A fc45ea51b1ec

Subscribe to this mod's changes

sdd-reverse-synth is a command published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 114 tokens to every session and 1,439 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-09-03.

Databases Planning

SDD-Pro: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/sdd-reverse-synth {LegacyProject} [--doc-level essentiel|complet|detaille] [--only c4,erd,soul] [--json]

Rôle

Args

Pré-conditions

Actions (no-spawn — script déterministe)

What this file has done since we first saw it

Other commands, from other repositories

init

security

database-setup

new-migration

json.batch_get

json.batch_delete