spec-intake

A project-specific command that turns a feature description into a written software specification using `.agent/workflows/spec-intake.md`.

In plain words
What is it for?
Use it to create a feature specification, flag points needing confirmation, and start the project setup after the specification is agreed.
Why use it?
It helps clarify the work, split multi-feature requests, identify assumptions, and record the result before implementation begins.

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/kbwen/agentic-os/spec-intake
Clone the repo
git clone --depth 1 https://github.com/KbWen/agentic-os

Made for: Claude Code.

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 149 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.00149
Opus 5 $0.00000 $0.00075
Sonnet 5 $0.00000 $0.00030
Haiku 4.5 $0.00000 $0.00015

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

Security

Grade A, and why

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/spec-intake.md · 21 lines

What it actually says

/spec-intake

Execute the canonical workflow: .agent/workflows/spec-intake.md

Required reads before execution

  1. .agentcortex/context/current_state.md — check for existing _product-backlog.md

Execution

Follow every step in .agent/workflows/spec-intake.md sequentially.

The user's spec input is: $ARGUMENTS

  • If multi-feature input: decompose into Feature Inventory, ask user which to start.
  • If single-feature: proceed directly to spec generation.
  • Generate docs/specs/<feature>.md with quality assessment.
  • Flag inferred items for user confirmation.
  • After spec is frozen, proceed to bootstrap automatically.
  • End response with ⚡ ACX.
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 · 21 lines · 0 tokens per session scan A 8c8d44735367

Subscribe to this mod's changes

spec-intake is a command published in the GitHub repository KbWen/agentic-os (149 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 149 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-30.