spec

A command for defining a project before coding begins. It asks clarifying questions, creates a structured specification, and saves it as SPEC.md for approval.

In plain words
What is it for?
Use it to agree on project objectives, commands, structure, coding rules, testing plans, and things the project must or must not do.
Why use it?
It reduces confusion about the goal, required behavior, technical limits, and boundaries before implementation starts.

Command for Claude Code

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/233i/agent-skills/spec
Clone the repo
git clone --depth 1 https://github.com/233i/agent-skills

Made for: Claude Code.

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 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.00017 $0.00161
Opus 5 $0.00009 $0.00081
Sonnet 5 $0.00003 $0.00032
Haiku 4.5 $0.00002 $0.00016

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

Security

Grade A, and why

spec 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.

.claude/commands/spec.md · 17 lines

What it actually says

调用 agent-skills:spec-driven-development

先弄清楚用户到底想构建什么,并通过提问澄清以下内容:

  1. 目标和目标用户是谁
  2. 核心功能与验收标准是什么
  3. 技术栈偏好和约束有哪些
  4. 已知边界是什么,例如哪些必须做、哪些要先问、哪些绝不能做

然后生成一份结构化 spec,覆盖六个核心区域:objective、commands、project structure、code style、testing strategy 和 boundaries。

将 spec 保存为项目根目录下的 SPEC.md,并在继续之前向用户确认。

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 · 17 lines · 17 tokens per session scan A 8abc1dee9a48

Subscribe to this mod's changes

spec is a command published in the GitHub repository 233i/agent-skills (6 stars, last pushed 4mo ago), licensed MIT. It adds 17 tokens to every session and 161 once invoked, about $0.0001 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.