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.
git clone --depth 1 https://github.com/cloudnative-co/claude-code-starter-kitWrote 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/cloudnative-co/claude-code-starter-kit/spec-kit-init)<a href="https://agentmods.dev/commands/cloudnative-co/claude-code-starter-kit/spec-kit-init"><img src="https://agentmods.dev/badge/commands/cloudnative-co/claude-code-starter-kit/spec-kit-init/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/cloudnative-co/claude-code-starter-kit/spec-kit-init"><img src="https://agentmods.dev/badge/commands/cloudnative-co/claude-code-starter-kit/spec-kit-init.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.00000 | $0.01437 |
| Opus 5.5 | $0.00000 | $0.00575 |
| Sonnet 5.5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
spec-kit-init 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-kit-init - Bootstrap GitHub Spec Kit in the current project
Initialize GitHub Spec Kit (Spec-Driven Development workflow) inside the
current project so that the /speckit-constitution, /speckit-specify,
/speckit-clarify, /speckit-plan, /speckit-tasks, and /speckit-implement
skills become available alongside the StarterKit's own commands.
This command is a thin guide layer — it does NOT install specify-cli
itself. You install specify-cli once per machine via uv (or pipx),
and this command shows you the canonical invocation for the current
project. The StarterKit deliberately stays decoupled from Spec Kit's release
cycle; uv tool upgrade specify-cli is how you keep Spec Kit current.
Instructions
You are entering Spec Kit Initialization. Walk the user through the 5 steps below in order. Do not execute heavy operations without confirmation; the user is in control.
Step 1 — Verify prerequisites
Run these checks and report their results to the user as a small table:
uv --version(required; install hint if missing:curl -LsSf https://astral.sh/uv/install.sh | sh)python3 --version(≥ 3.10 required byspecify-cli)git --version(required)claude --version(Claude Code itself; should already be installed if you're reading this)
If any of the first three are missing, STOP and ask the user how they want to proceed (install via Homebrew? via official installer? skip?). Do not run installers without explicit consent.
Step 2 — Install or update specify-cli (user-scope)
If specify --version does not return a version, run:
LATEST_TAG=$(gh api repos/github/spec-kit/releases/latest --jq .tag_name)
uv tool install specify-cli --from "git+https://github.com/github/spec-kit.git@${LATEST_TAG}"
If specify is already installed, offer to upgrade:
uv tool upgrade specify-cli
Confirm with specify --version and specify check | grep -i claude
(the latter must show Claude Code (available)).
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 · 118 lines · 0 tokens per session scan E 1308bcdb657f
spec-kit-init is a command published in the GitHub repository cloudnative-co/claude-code-starter-kit (153 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,437 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.