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 skills/github/spec-kit-copilot/speckit-presetnpx skills add github/spec-kit-copilot --skill speckit-presetgit 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.00088 | $0.00725 |
| Opus 5 | $0.00044 | $0.00362 |
| Sonnet 5 | $0.00018 | $0.00145 |
| Haiku 4.5 | $0.00009 | $0.00072 |
Grade A, and why
speckit-preset 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec Kit — presets
Manage spec-kit presets with the Specify CLI specify preset command group.
Presets bundle templates/configuration for a particular domain or workflow.
Prerequisite: needs the
specifyCLI. Ifspecify --versionfails, install it with the speckit-cli-setup skill first.
When to use
- Find, install, or remove a preset.
- Check which template a preset name resolves to.
- Enable/disable a preset or adjust its resolution priority.
How to invoke
# Discover
specify preset list
specify preset search <query>
specify preset info <id>
specify preset resolve <name> # show which template a name resolves to
# Install
specify preset add <id>
specify preset add --from <url> # install from a ZIP URL
specify preset add --dev <path> # install from a local directory
specify preset add <id> --priority <n> # lower number = higher precedence
# Lifecycle
specify preset enable <id>
specify preset disable <id>
specify preset set-priority <id> <n>
specify preset remove <id>
# Catalogs (sources presets are resolved from)
specify preset catalog list
specify preset catalog add <url> --name <name> [--install-allowed]
specify preset catalog remove <name>
Notes
- Resolution priority: lower number = higher precedence (default
10). - Catalogs are added discovery-only by default.
specify preset catalog addrequires--nameand defaults to--no-install-allowed; presets from a discovery-only catalog can be browsed but not installed (install errors with a "discovery-only" message). Pass--install-allowedto permit installs — only for catalogs you trust. Theinstall_allowedpolicy lives in the consumer's.specify/preset-catalogs.yml, not in the catalog's owncatalog.json. - A preset can also be installed at project creation:
specify init <name> --integration copilot --integration-options="--skills" --script sh --preset <id>(use--script pson Windows; see the speckit-init skill for the full OS-aware form and why--scriptis required). - Use
specify preset resolveto debug unexpected template resolution. - Unlike extensions/bundles,
specify preset adddoes not scaffold skills — a preset overrides the templates used to generate command content and is applied at init time./skills reloadonly matters if a regeneration actually changesSKILL.mdfiles under.github/skills/.
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.
- 2d ago First seen · 66 lines · 88 tokens per session scan A 6073cda9387a
speckit-preset is a skill published in the GitHub repository github/spec-kit-copilot (11 stars, last pushed 6d ago), licensed MIT. It adds 88 tokens to every session and 725 once invoked, about $0.0004 per session on Opus 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…
external-comms
PAO workflow for scanning, drafting, and presenting community responses with human review gate.
distributed-mesh
How to coordinate with squads on different machines using git as transport.
tiered-memory
Three-tier agent memory model (hot/cold/wiki) for context reduction per spawn.
client-compatibility
Platform detection and adaptive spawning for CLI vs VS Code vs other surfaces.
init-mode
Team initialization flow (Phase 1 proposal + Phase 2 creation).