index

A command reference for a specification workflow in Claude Code and Codex. It maps commands such as starting a feature specification, brainstorming, checking progress, and creating tasks.

In plain words
What is it for?
Use it to find commands for planning features, writing bug-fix specifications, refining requirements, checking status, and regenerating task lists.
Why use it?
It removes uncertainty about which command to run and whether to use the `/` or `$` prefix in each coding tool.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/habib0x0/spec-driven-plugin/index
Clone the repo
git clone --depth 1 https://github.com/Habib0x0/spec-driven-plugin
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,085 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01085
Opus 5 $0.00000 $0.00543
Sonnet 5 $0.00000 $0.00217
Haiku 4.5 $0.00000 $0.00109

Measured 2d ago against content hash 89b32c0646b2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

index 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 2d 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.

docs/commands/index.md · 71 lines

How it starts

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

Command reference

Commands use / prefix in Claude Code and $ prefix in Codex. Execution scripts (spec-loop.sh, spec-exec.sh, etc.) are run from the terminal in your project root.

Claude Code Codex Description
/spec $spec Start a new feature spec
/spec-brainstorm $spec-brainstorm Brainstorm a feature idea
/spec-bugfix $spec-bugfix Start a bugfix spec
/spec-status $spec-status Check spec progress

Planning commands

Claude Code Codex Description Example
/spec-brainstorm $spec-brainstorm Brainstorm a feature idea with optional expert consultants. /spec-brainstorm user notifications
/spec <name> $spec <name> Start a new feature spec (Requirements, Design, Tasks). /spec user-authentication
/spec-bugfix <name> $spec-bugfix <name> Start a bugfix spec with regression prevention. /spec-bugfix email-validation-plus-sign
/spec-refine $spec-refine Update requirements or design; cascades to tasks. /spec-refine
/spec-tasks $spec-tasks Regenerate tasks.md from current design. /spec-tasks

Status and validation commands

Claude Code Codex Description Example
/spec-status $spec-status Show progress, task counts, dependency status. /spec-status
/spec-validate $spec-validate Validate EARS notation, coverage, traceability. /spec-validate

Execution commands

Claude Code Codex Description Example
/spec-exec $spec-exec Run one implementation iteration. /spec-exec
/spec-loop $spec-loop Loop until all tasks are verified. /spec-loop

Post-implementation commands

Claude Code Codex Description Example
/spec-accept $spec-accept Acceptance testing against EARS criteria. /spec-accept
/spec-docs $spec-docs Generate docs from spec and implementation. /spec-docs
/spec-release $spec-release Release notes, changelog, deployment checklist. /spec-release
/spec-verify $spec-verify Post-deployment smoke tests against a URL. /spec-verify
/spec-retro $spec-retro Retrospective on a completed spec. /spec-retro
/spec-complete $spec-complete Full pipeline: accept → docs → release → retro. /spec-complete

Read the full file on GitHub · 71 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.

  1. 2d ago First seen · 71 lines · 0 tokens per session scan A 89b32c0646b2

Subscribe to this mod's changes

index is a command published in the GitHub repository Habib0x0/spec-driven-plugin (10 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,085 tokens. 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-31.