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/docs.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/docs)<a href="https://agentmods.dev/commands/dinhnguyenngoc/spec-driven-claude-code/docs"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/docs/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/docs"><img src="https://agentmods.dev/badge/commands/dinhnguyenngoc/spec-driven-claude-code/docs.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.00006 | $0.04273 |
| Opus 5.5 | $0.00002 | $0.01709 |
| Sonnet 5.5 | $0.00001 | $0.00855 |
| Haiku 4.5 | $0.00001 | $0.00427 |
Grade A, and why
docs scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl http://localhost:5000/swagger/v1/swagger.json > docs/api/openapi.json How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/docs — Documentation
"If it's not documented, it doesn't exist."
Purpose
Consolidate existing documentation and complete missing pieces before deployment. Ensure all technical artifacts from previous phases are properly linked and accessible.
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.
Principle: Don't duplicate — link and reference existing artifacts from
/spec,/arch,/secure,/infra.
Stack Profile note: read
Project Profilefirst. Core = Node.js → generate API docs from the framework's OpenAPI tooling (@nestjs/swagger, Fastify schema-first — seerules/overrides/framework-nodejs-web.md), and thedotnet/DocFX commands in Phase 4 & §Auto-Generation Tools map to their npm equivalents. Core = PHP → API docs come from the Laravel tooling (scribeorl5-swagger, orphp artisan route:listcross-checked againstarchitecture/api/openapi.yaml), not Swashbuckle/DocFX; thedotnetcommand blocks in Phase 2 (Quick Start) and Phase 6 (Deployment Guide) map tocomposer install --no-dev --optimize-autoloader,php artisan migrate --force, andphp artisan serve/ the fpm-nginx or Octane container shape fromrules/overrides/framework-php-laravel.md§J. The templates stay default-stack illustration — their "example only" disclaimers apply; DB/observability lines follow the Profile +rules/overrides/*.
Prerequisites
- Implementation complete (
/builddone) - Infrastructure setup (
/infradone) - API contracts defined (
architecture/api/)
Workflow
Run mode — first-run vs incremental.
docs/largely absent → first-run: generate the full set (Phases 1-6).docs/already exists → incremental: update only the docs the change touched +CHANGELOG.md; leave unchanged docs alone. Delta → doc map:
- new/changed endpoint →
docs/api/+CHANGELOG.md- new env var →
configuration.md- fixed bug (BUG-### in
TEST_REPORT.md) →troubleshooting.md- setup / run / deploy steps changed →
getting-started.md+deployment.md- any release →
CHANGELOG.md- When unsure whether a doc is affected → regenerate it (don't risk staleness).
- Before a major release, do a full-set pass (treat as first-run) to catch drift.
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 · 410 lines · 6 tokens per session scan A e0a3c5c17231
docs is a command published in the GitHub repository dinhnguyenngoc/spec-driven-claude-code (21 stars, last pushed 2mo ago), licensed MIT. It adds 6 tokens to every session and 4,273 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
kiro-validate-design
Command "kiro-validate-design" from gotalab/cc-sdd, covering technical design validation, core task, execution steps, important constraints and tool guidance.
type-coverage
Vérification Couverture des Types Python.
generate-adapter
Erstellt ein Paperclip-Extension-Gerüst (Plugin via create-paperclip-plugin oder Built-in-Adapter).
wayfind
Plan a chunk of work too big for one agent session as a shared decision map: map.md + typed decision tickets in the mega-goal folder, resolved one per session through the kit's own grill/prototype/research machinery, until nothing is left to decide. Then hand off to /kit:spec or a ROADMAP, never straight to execute.
devs-team
Parallel multi-lens critique of a solution design (the active spec if present, else the decision brief). Dispatches 5 engineering lenses, merges findings, reports a verdict. Report-only, never blocks.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode), issue tracker.