spec-driven-development

A development process that requires a detailed product requirements document before coding starts. The document covers goals, design, testing, limits, and success conditions.

In plain words
What is it for?
Planning software changes, reviewing specifications, and defining how the finished work will be tested.
Why use it?
It makes the intended work and boundaries clear before implementation begins.

Skill for Claude CodeCodex

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 skills/codexskills/agent-forge/spec-driven-development
Any agent
npx skills add codexskills/agent-forge --skill spec-driven-development
Clone the repo
git clone --depth 1 https://github.com/codexskills/agent-forge

Made for: Claude Code, Codex.

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,513 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00049 $0.02513
Opus 5 $0.00024 $0.01256
Sonnet 5 $0.00010 $0.00503
Haiku 4.5 $0.00005 $0.00251

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

Security

Grade A, and why

spec-driven-development 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 yesterday.

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.

skills/spec-driven-development/SKILL.md · 253 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 253 lines · 49 tokens per session scan A 2f5f8cd7159d

Subscribe to this mod's changes

spec-driven-development is a skill published in the GitHub repository codexskills/agent-forge (1 stars, last pushed 2mo ago), with no licence file. It adds 49 tokens to every session and 2,513 once invoked, about $0.0002 per session on Opus 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-31.