Borrowing it
Nothing to install: this file belongs to dinhnguyenngoc/spec-driven-claude-code. 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/dinhnguyenngoc/spec-driven-claude-code/main/.claude/commands/build.mdgit clone --depth 1 https://github.com/dinhnguyenngoc/spec-driven-claude-codeWrote 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/dinhnguyenngoc/spec-driven-claude-code/build)<a href="https://agentmods.dev/commands/dinhnguyenngoc/spec-driven-claude-code/build"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/build/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/dinhnguyenngoc/spec-driven-claude-code/build"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/build.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.00012 | $0.04762 |
| Opus 5.5 | $0.00005 | $0.01905 |
| Sonnet 5.5 | $0.00002 | $0.00952 |
| Haiku 4.5 | $0.00001 | $0.00476 |
Grade A, and why
build 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/build — Incremental Implementation
"The simplest thing that could work."
Purpose
Implement tasks one at a time using Test-Driven Development. Each increment leaves the system in a working, testable state.
Workspace Mode: if the session root declares
Mode: workspace→ resolve the target repo perCLAUDE.md§Workspace Mode before anything else; every path, probe, and gate below is relative to the target repo, and the workspace disk-check applies at the gate.
Stack Profile note: examples + commands below use the default profile (C#/.NET + SQL Server). Read
Project Profile(.claude/PROJECT_PROFILE.md) first: Core = Node.js →rules/overrides/lang-nodejs.md+framework-nodejs-web.md+test-nodejs.mdreplace the language/framework/test layers — thedotnetcommands in this file map to their npm equivalents (npm test,tsc --noEmit,npm run build; in-memory integration template pertest-nodejs.md§Template A). Database ≠ SQL Server →rules/overrides/database-*.md(Oracle / MySQL / PostgreSQL / MongoDB) for data access + test setup. Brownfield: followrules/brownfield.md(characterization test before modifying legacy code that has no tests).
Prerequisites
Required:
- A plan exists —
plans/plan.md(task detail: AC, Scenarios covered, NFRs covered (when the task delivers an NFR mechanism), Files to modify, Tests to add) +plans/todo.md(the actionable checklist) - Understanding of task acceptance criteria
- The declared core's SDK installed — .NET SDK 8.0 (default) | Node.js 20 LTS (when the Profile declares Node core)
Optional (if available):
- Pre-development security review (
security/PRE_DEV_REVIEW.mdfrom/secure) — if/securewas run, it must be marked APPROVED before building (Gate 4 is BLOCKING if run) - Threat model (
security/THREAT_MODEL.mdfrom/secure)
Agent Selection
| Task Type | Agent to Invoke |
|---|---|
| APIs, services, DB, background jobs | 🔧 Backend Developer |
| Components, pages, routing, UI | 🖥️ Frontend Developer |
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 · 337 lines · 12 tokens per session scan A a167f4dc5059
build is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 4,762 once invoked, about $0.0000 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
spec-impl
Execute spec tasks using TDD methodology.
kiro-spec-impl
Command "kiro-spec-impl" from gotalab/cc-sdd, covering implementation task executor, core task, execution steps, step 1: load context and step 2: select tasks.
workflow-implement
Exécuter la phase d'Implémentation - développement TDD/BDD d'un sprint, d'un epic, d'une story ou de la file batch (séquentiel, ou parallèle via /team:sprint).
fix
Correction automatisee des bugs identifies par la QA Recette.
tdd
Correction de Bug en Mode TDD/BDD.
build
Run /build — see .claude/commands/build.md for the authoritative spec.