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/dev-frontend.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/dev-frontend)<a href="https://agentmods.dev/commands/zekiriabd/sdd-pro/dev-frontend"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/dev-frontend/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/dev-frontend"><img src="https://agentmods.dev/badge/commands/zekiriabd/sdd-pro/dev-frontend.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.00017 | $0.00741 |
| Opus 5.5 | $0.00007 | $0.00296 |
| Sonnet 5.5 | $0.00003 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
dev-frontend 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/dev-frontend — Génère le code client d'UNE US
⚠️ Commande interne v7.0.0 — invoquée par
/dev-runSTEP 6.c (batch 1 US). Utilisateur final : préférer/sdd-fullou/dev-run(gèrent pré-conditions, idempotence, état).
Invoque l'agent dev-frontend pour matérialiser l'US
workspace/us/{n}-{m}-{Name}.md + le mockup HTML éventuel
workspace/ui/{n}-{m}-{Name}.html en code client (Pages, Components,
Layouts, theme.css, bootstrap HTML). L'agent planifie inline les
fichiers à produire à partir de l'US + du mockup HTML + des stacks
frontend/ui actifs.
Si l'US n'a aucune contrepartie frontend (US backend pure), l'agent
exit silencieusement avec une ligne skipped (backend-only US).
1 invocation = 1 US = 1 build frontend. Pour traiter plusieurs US,
lancer la commande plusieurs fois ou utiliser /dev-run {n}.
Usage : /dev-frontend {n}-{m} — où {n}-{m} cible une US existante
(ex. /dev-frontend 1-2).
STEP 1 — Valider l'argument
Argument obligatoire : {n}-{m}.
Si absent → demander :
Quelle est l'US à matérialiser côté frontend ? (format : {n}-{m}, ex. 1-2)
Si format invalide →
ERROR: /dev-frontend — argument invalide
CAUSE: [INVALID_ARG] "{argument}" ne respecte pas le format {n}-{m}
FIX: relancer /dev-frontend {n}-{m} (ex. /dev-frontend 1-2)
STEP 2 — Invoquer l'agent dev-frontend
Lancer l'agent dev-frontend (défini dans .claude/agents/dev-frontend.md)
avec l'argument {n}-{m}. L'agent gère :
- la lecture sélective de l'US, du mockup HTML, des stacks frontend + UI actifs
- le plan inline des fichiers client (ou exit silencieux si US backend-only)
- la génération de code conforme au mapping du stack (HTML brut traduit en composants natifs DS)
- le build loop (max 3 itérations)
- la vérification de fidélité textuelle (libellés HTML présents dans le markup généré)
- la confirmation 1 ligne
Attendre la fin de l'agent. Relayer sa sortie telle quelle.
STEP 3 — Confirmation finale
Si l'agent réussit avec génération, ajouter UNE SEULE ligne :
Prochaine étape : si l'US a une partie backend, lancer /dev-backend {n}-{m}.
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 · 83 lines · 17 tokens per session scan A 9b64f90b1ffd
dev-frontend is a command published in the GitHub repository zekiriabd/SDD-Pro (196 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 17 tokens to every session and 741 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.