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-cli-setupgit 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-cli-setup)<a href="https://agentmods.dev/skills/github/spec-kit-copilot/speckit-cli-setup"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-cli-setup/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-cli-setup"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-cli-setup.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.00100 | $0.00767 |
| Opus 5.5 | $0.00040 | $0.00307 |
| Sonnet 5.5 | $0.00020 | $0.00153 |
| Haiku 4.5 | $0.00010 | $0.00077 |
Grade C, and why
speckit-cli-setup scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
(`curl -LsSf https://astral.sh/uv/install.sh | sh`, or see <https://docs.astral.sh/uv/>), Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
(`curl -LsSf https://astral.sh/uv/install.sh | sh`, or see <https://docs.astral.sh/uv/>), How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit — CLI setup
The Spec Kit plugin drives the specify command-line tool. Every other speckit
skill assumes specify is installed and on PATH. This skill detects it and
installs it when it is missing.
Detect first
Always check availability before doing anything else:
specify --version
- Prints a version (e.g.
specify 0.15.0) → the CLI is installed. If a skill needsbundleorworkflow step, ensure the version is >= 0.11; if it is older, hand off to the speckit-self skill to upgrade. command not found/ non-zero exit → not installed. Install it (below).
Install
Spec Kit's specify CLI is published on PyPI as
specify-cli. Install the latest
release — this plugin is not pinned to a specific specify version.
uv is the recommended installer;
pipx is an alternative:
# Recommended: uv (persistent install, latest from PyPI)
uv tool install specify-cli
# Alternative: pipx (persistent install, latest from PyPI)
pipx install specify-cli
# One-off / ephemeral (no install) — handy to bootstrap a project.
# Pass --script (py keeps this cross-platform) so the PTY-backed agent shell
# doesn't hit the interactive "Choose script type" chooser and hang.
uvx --from specify-cli specify init . --integration copilot --integration-options="--skills" --script py
If neither uv nor pipx is available, tell the user to install uv first
(curl -LsSf https://astral.sh/uv/install.sh | sh, or see https://docs.astral.sh/uv/),
then re-run the install. Do not silently install system Python packages.
Verify
specify --version
specify check
Notes
- This skill is the prerequisite for the rest of the plugin. If any speckit skill
finds that
specifyis not available, it should run this skill's detect/install steps first, then retry. - For an already-installed CLI that just needs a newer version, prefer the
speckit-self skill (
specify self upgrade) over reinstalling. To refresh auv/pipxinstall to the latest PyPI release, useuv tool upgrade specify-cliorpipx upgrade specify-cli. - Installing from PyPI always pulls the latest published
specify-cli. Only pin a specific version (e.g.uv tool install "specify-cli==0.15.0") if you have a concrete reason to hold back.
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 · 70 lines · 100 tokens per session scan C 20868208c81e
speckit-cli-setup is a skill published in the GitHub repository github/spec-kit-copilot (18 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 767 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). 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…