A runtime command that starts the generated backend, frontend, and project console as separate background processes. It can start all three or only the parts you select.

Use it to run the backend, frontend, console, or a selected combination during local development. It does not build or modify the generated code.

It removes the need to launch each development process separately when checking a generated project. It reads the active project configuration to find the relevant applications.

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-serve.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-serve/github.svg)](https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-serve)

Your own site

<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/sdd-serve"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-serve/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-serve"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/sdd-serve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,494 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.00018	$0.02494
Opus 5.5	$0.00007	$0.00998
Sonnet 5.5	$0.00004	$0.00499
Haiku 4.5	$0.00002	$0.00249

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

Security

Grade A, and why

sdd-serve 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-serve.md · 249 lines

How it starts

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

/sdd-serve — Lance backend + frontend + console en parallèle

Renommée v7.0.0 : ex-/sdd-run (renommée pour lever l'ambiguïté UX avec /sdd-full — orchestrateur pipeline — et /dev-run — orchestrateur dev). /sdd-serve est un utilitaire runtime read-only, jamais un orchestrateur.

Démarre les 3 process runtime du projet généré en arrière-plan :

Backend ({BackendName}) — selon stack actif
Frontend ({FrontendName} aka {AppName}) — selon stack actif
Console SDD (workspace/console/) — cockpit de validation

Lecture seule sur le code généré, aucune invocation d'agent, aucun build. Chaque process tourne en run_in_background ; les logs sont accessibles via BashOutput / Monitor sur le shell parent.

Usage :

/sdd-serve — lance les 3
/sdd-serve back — backend seul
/sdd-serve front — frontend seul
/sdd-serve console — console seule
/sdd-serve back front — combinaison (sous-ensemble)

STEP 1 — Charger Project Config

Read workspace/stack/stack.md § ## Project Config :

FrontendName (ou alias AppName) → répertoire frontend
BackendName → répertoire backend

Read ## Active Tech Specs pour identifier :

Backend stack : backend/kotlin-spring-boot | backend/dotnet-minimalapi | backend/python-fastapi | backend/node-express
Frontend stack : frontend/react | frontend/vue | frontend/angular | frontend/blazor-webassembly

Si ## Project Config absent OU FrontendName/BackendName non lisibles :

ERROR: /sdd-serve — Project Config incomplet
CAUSE: [STACK_MALFORMED] FrontendName ou BackendName absent de workspace/stack/stack.md
FIX: renseigner FrontendName et BackendName dans ## Project Config

STEP 2 — Résoudre la commande de run par stack

Backend

Stack actif	Répertoire	Commande de run
`backend/kotlin-spring-boot`	`workspace/src/{BackendName}/`	`./gradlew bootRun` (Python : `.\gradlew.bat bootRun`)
`backend/dotnet-minimalapi`	`workspace/src/{BackendName}/`	`dotnet run --project {BackendName}.csproj`
`backend/python-fastapi`	`workspace/src/{BackendName}/`	`uvicorn app.main:app --reload --port 8000`
`backend/node-express`	`workspace/src/{BackendName}/`	`npm run dev` (fallback `npm start`)
`fullstack/*`	`workspace/src/{BackendName}/`	suivre §1 du stack fullstack

Read the full file on GitHub · 249 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 · 249 lines · 18 tokens per session scan A 0e13342af75c

Subscribe to this mod's changes

sdd-serve is a command published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 2,494 once invoked, about $0.0001 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.

DevOps and cloud Frontend

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-serve — Lance backend + frontend + console en parallèle

STEP 1 — Charger Project Config

STEP 2 — Résoudre la commande de run par stack

Backend

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

speckit.bug.fix

speckit.bug.test