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.
npx agentmods add commands/github/spec-kit-copilot/speckit.plangit clone --depth 1 https://github.com/github/spec-kit-copilotWhat 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 | $0.00000 | $0.00448 |
| Opus 5 | $0.00000 | $0.00224 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
speckit.plan 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.
How it starts
The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sub-Agent Delegation
When executing this command, delegate independent work to parallel sub-agents to reduce total execution time.
How to dispatch sub-agents in Copilot:
- VS Code: Use the
runSubagenttool to spawn each sub-agent in an isolated context. - CLI: Delegate to a sub-agent process — Copilot CLI automatically manages subsidiary sub-agent execution. You can also target custom agents defined in
.github/agents/or~/.copilot/agents/.
Phase 0 — Research in Parallel
When generating research tasks for unknowns in Technical Context, dispatch each research topic as a separate sub-agent:
-
For each NEEDS CLARIFICATION item in Technical Context: → Sub-agent: "Research {unknown} for {feature context}. Return: Decision, Rationale, Alternatives considered."
-
For each technology choice needing best-practices review: → Sub-agent: "Find best practices for {tech} in {domain}. Return: recommended patterns, pitfalls, configuration guidance."
Launch all research sub-agents in parallel, then consolidate their results into research.md.
Phase 1 — Design Artifacts
After research.md is complete, generate the design artifacts. Two of them are independent and one depends on their output, so dispatch them in two waves:
Wave 1 (parallel):
- Sub-agent: Data Model — "Extract entities from the feature spec and research findings. Generate
data-model.mdwith entity names, fields, relationships, validation rules, and state transitions." - Sub-agent: Interface Contracts — "Define interface contracts for the project based on the spec and research. Generate files under
contracts/documenting exposed interfaces."
Wait for both to complete.
Wave 2 (after Wave 1):
- Sub-agent: Quickstart — "Create
quickstart.mdwith integration scenarios and getting-started guidance based on the spec, data model, and contracts." (Requiresdata-model.mdandcontracts/from Wave 1.)
Once all three artifacts exist, proceed to agent context update and constitution re-evaluation.
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.
- yesterday First seen · 39 lines · 0 tokens per session scan A be0e5fca6075
speckit.plan is a command published in the GitHub repository github/spec-kit-copilot (11 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 448 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
spec-kitty.analyze
Spec-Driven Development for serious software developers. Spec Coding with with Claude, Cursor, Gemini, Codex. Kanban dashboard, git worktrees, auto-merge and more.
sdd-plan
Turn a spec into a persisted baby-step plan file — research, resume, impact analysis.
sdd-setup
Onboarding wizard — DocLanguage, Memory Bank, architecture snapshot, working agreements (quality gate, TDD working mode).
sdd-clarify
Adversarial pass over a finished spec — contradictions, ambiguity, untestable criteria, implementation posing as intent, missing failure modes.
plan
Run /plan — see .claude/commands/plan.md for the authoritative spec.
epic-plan
Run /epic-plan — see .claude/commands/epic-plan.md for the authoritative spec.