github/spec-kit-copilot is a repository of GitHub Copilot integrations for Spec Kit, a toolkit for developing software through a structured specification-first workflow. It provides Copilot-specific commands, skills, canvases, and related workflow components for users of the Copilot CLI, Copilot App, and VS Code.
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 skills add github/spec-kit-copilot --skill speckit-workflow-stepgit clone --depth 1 https://github.com/github/spec-kit-copilotWrote 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/skills/github/spec-kit-copilot/speckit-workflow-step)<a href="https://agentmods.dev/skills/github/spec-kit-copilot/speckit-workflow-step"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-workflow-step/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/skills/github/spec-kit-copilot/speckit-workflow-step"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-workflow-step.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00084 | $0.00401 |
| Opus 5.5 | $0.00034 | $0.00160 |
| Sonnet 5.5 | $0.00017 | $0.00080 |
| Haiku 4.5 | $0.00008 | $0.00040 |
Grade A, and why
speckit-workflow-step 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.
What it actually says
Spec Kit — workflow step types
Manage the step types that workflows are composed of, using the Specify CLI
specify workflow step command group. (Requires Specify CLI >= 0.11.)
Prerequisite: needs the
specifyCLI. Ifspecify --versionfails, install it with the speckit-cli-setup skill first.
When to use
- Inspect which step types (built-in or custom) are available to workflows.
- Install or remove a custom step type, or manage step-type catalog sources.
How to invoke
# Discover step types
specify workflow step list
specify workflow step search <query>
specify workflow step info <step-id>
# Install / remove custom step types
specify workflow step add <step-id> # from the step catalog
specify workflow step remove <step-id>
# Manage step catalog sources
specify workflow step catalog list
specify workflow step catalog add <url>
specify workflow step catalog remove <index> # by index
Notes
- Step types are the building blocks referenced by workflow YAML; install the step types a workflow needs before running it (see the speckit-workflow skill).
listshows both built-in and custom step types; only custom ones can be removed.
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 · 43 lines · 84 tokens per session scan A ad46e550e0a7
speckit-workflow-step is a skill published in the GitHub repository github/spec-kit-copilot (18 stars, last pushed today), licensed MIT. It adds 84 tokens to every session and 401 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
brag-sheet
Turns vague "what did I do?" into evidence-backed impact statements for performance reviews, self-reviews, promotion packets, and weekly updates. Uniquely mines Copilot CLI session logs to reconstruct forgotten work, plus git commits and GitHub PRs. Enforces a 3-part impact contract (action → result → evidence). Works…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-next
Drive the canonical spec-kitty next --mission control loop for mission advancement. Load agent profiles at init, apply action-scoped doctrine context at each step boundary, and pull specific tactics/directives on demand. Triggers: "run the next step", "what should runtime do next", "advance the mission", "what is the…
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…