A development command that coordinates the implementation of one feature across architecture, database setup, server code, API checks, and user-interface code. An API is the interface through which software components exchange data.

Use it to implement all user stories in a feature, including server endpoints and interface work, while running the API gate between them.

It keeps dependent development stages in order and runs suitable independent user stories together. This reduces the need to invoke each development stage manually.

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

Your own site

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

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

When invoked 11,488 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.00027	$0.11488
Opus 5.5	$0.00011	$0.04595
Sonnet 5.5	$0.00005	$0.02298
Haiku 4.5	$0.00003	$0.01149

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

Security

Grade A, and why

dev-run 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/dev-run.md · 920 lines

How it starts

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

/dev-run — Orchestrateur dev (arch+db → back → API gate → front) pour 1 FEAT

Commande user-facing (cf. CLAUDE.md §3 — 13 user-facing). Phase 4 : orchestre arch+DB → dev-backend ALL US → QA API Gate → dev-frontend ALL US. Invoquée aussi par /sdd-full STEP 4. Pour un pipeline complet A→Z, préférer /sdd-full qui gère également Phase 2 (US) et Phase 5 (QA + reviews).

Dépendance load-bearing au runtime Claude Code : orchestration parallèle via tool Agent (alias Task) avec N calls indépendants dans un même message. Contrat externe garanti par Claude Code. Anti-régression : framework_smoke.py vérifie la présence de « parallèle » + Agent + dev-backend + dev-frontend.

Pour la FEAT {n}, en séquence (workflow gated séquentiel depuis v7.0.0, default GatedWorkflow: true — cf. STEP 6 et .sdd/rules/build-and-loop.md Partie A) :

Pré-step arch (idempotent) — bootstrap solution/projets selon stacks actifs + scaffolding DB Database-First si DatabaseType ≠ none (les deux phases sont gérées par le même agent arch)
dev-backend sur TOUTES les US (parallélisme intra-back borné par MaxParallel, default 3 US simultanées)
QA API Gate (tests d'intégration HTTP in-memory) — STOP si status=FAIL|INFRA_BLOCKED, continue sur PASS|WARN|SKIPPED
dev-frontend sur TOUTES les US (parallélisme intra-front borné par MaxParallel) ; chaque agent décide s'il a du travail (frontend pure / backend pure) ou exit silencieux

Anti-régression : framework_smoke.py valide la présence de Agent + parallèle + dev-backend + dev-frontend dans ce fichier (le parallélisme intra-phase reste un contrat load-bearing du runtime Claude Code). Le sequencing inter-phase back→gate→front est la nouveauté v7.0.0 vs v6.x parallèle. Legacy v6 disponible via GatedWorkflow: false (audit-log legacy-parallel.log).

Mode autonome : pas de Q/R utilisateur.

Usage : /dev-run {n} ({n} = numéro FEAT).

Hors scope : /us-generate doit avoir tourné avant. Consomme workspace/us/ (US) et workspace/ui/ (mockups HTML optionnels).

Read the full file on GitHub · 920 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 · 920 lines · 27 tokens per session scan A 67996bb021e5

Subscribe to this mod's changes

dev-run is a command published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 11,488 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-08-30.

Backend and APIs Frontend

init

Initialize configurations for Supabase local development.

fcakyon/claude-codex-settings · 0 tokens

http-service

Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.

MadAppGang/magus · 27 tokens

api-contract-review

Review an API contract (shapes, errors, auth model) BEFORE implementation for naming, versioning, pagination, idempotency, and fit with existing endpoints. Use when designing or changing endpoints. Do not use when the API is already implemented (use review-hard or repo-consistency-sweep).

Mozurok/fhorja.dev · 64 tokens

build

Discover an AI Gateway's models and MCP tools, retrieve a credential, and integrate them into your app — call a model, connect MCP tools, or scaffold a runnable agent.

Azure/ai-gateway · 0 tokens

start-10-1

A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.

minicoohei/ai-agent-camp · 2 tokens

fastapi

FastAPI application design and implementation conventions. Use this skill when building, updating, or reviewing FastAPI services, routers, dependencies, request/response schemas, streaming endpoints, or API tests. Trigger on FastAPI-specific work such as path operation design, dependency injection, response models…

mfmezger/ai_agent_dotfiles · 84 tokens

SDD-Pro: Command for Claude Code