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-artifactgit 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-artifact)<a href="https://agentmods.dev/skills/github/spec-kit-copilot/speckit-artifact"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-artifact/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-artifact"><img src="https://agentmods.dev/badge/skills/github/spec-kit-copilot/speckit-artifact.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.00105 | $0.00702 |
| Opus 5.5 | $0.00042 | $0.00281 |
| Sonnet 5.5 | $0.00021 | $0.00140 |
| Haiku 4.5 | $0.00011 | $0.00070 |
Grade A, and why
speckit-artifact 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit — artifacts
Inspect commands, templates, scripts, hooks, and their effective composition
stacks with the Specify CLI specify artifact command group. Requires
Specify CLI >= 1.0.7.
Prerequisite: needs the
specifyCLI. Ifspecify --versionfails, install it with the speckit-cli-setup skill first.
When to use
- List every command, template, script, and hook visible to a Spec Kit project.
- Explain which project, preset, extension, or built-in layer supplies an artifact.
- Inspect precedence, composition strategy, active layers, and hidden layers.
- Check whether declared hooks are registered and active.
- Resolve a stack entry back to the validated manifest contribution Spec Kit uses.
How to invoke
# Full artifact inventory, including composition stacks
specify artifact list --json
# Inspect one artifact by bare name or source-agnostic artifact id
specify artifact info <name> --json
specify artifact info <kind>:<name> --json
specify artifact info <name> --kind <command|template|script|hook> --json
# Resolve a manifest-backed stack layer to its effective contribution
specify artifact lookup <lookupId> --json
Identifiers
- An artifact
idhas the form<kind>:<name>, such ascommand:speckit.specify. Pass this value tospecify artifact info. - A stack entry's
lookupIdidentifies the preset or extension contribution behind that layer. Pass this opaque value unchanged tospecify artifact lookup. - Built-in layers do not have a
lookupId. Project or convention-only layers may not have a manifest contribution thatlookupcan resolve.
Notes
- All
specify artifactsubcommands are read-only. --jsonis currently required. A missing--jsonis a usage error.- Run commands from an initialized Spec Kit project containing
.specify/. listandinforeturn ordered stacks. For commands, templates, and scripts, index0is the winning layer. Hook stacks are additive, so multiple entries can be active.- Composition strategies are
replace,wrap,prepend,append, andadditivefor hooks. activeandhiddenare independent: an inactive layer can still participate in composed output unless a higherreplacelayer hides it.- Hook artifact ids percent-encode event and target-command components. Reuse ids and lookupIds exactly as returned instead of constructing them manually.
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 · 63 lines · 105 tokens per session scan A 7331f894426b
speckit-artifact is a skill published in the GitHub repository github/spec-kit-copilot (18 stars, last pushed today), licensed MIT. It adds 105 tokens to every session and 702 once invoked, about $0.0004 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-09-17.
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…