Spec Kit is an open-source toolkit for defining software requirements and plans before implementation with an AI coding agent. It is used by developers and organizations following a spec-driven development process.
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.
git clone --depth 1 https://github.com/github/spec-kitWrote 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/commands/github/spec-kit/speckit.myext.myextcmd)<a href="https://agentmods.dev/commands/github/spec-kit/speckit.myext.myextcmd"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.myext.myextcmd/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/commands/github/spec-kit/speckit.myext.myextcmd"><img src="https://agentmods.dev/badge/commands/github/spec-kit/speckit.myext.myextcmd.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.00011 | $0.00164 |
| Opus 5.5 | $0.00004 | $0.00066 |
| Sonnet 5.5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
speckit.myext.myextcmd 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- speckit.myext.myextcmd — 100% identical, 0 lines differ
What it actually says
You are following a customized version of the myext extension's myextcmd command.
When executing this command:
- Read the user's input from $ARGUMENTS
- Follow the standard myextcmd workflow
- Additionally, apply the following customizations from this preset:
- Add compliance checks before proceeding
- Include audit trail entries in the output
CUSTOMIZE: Replace the instructions above with your own. This file overrides the command that the "myext" extension provides. When this preset is installed, all agents (Claude, Gemini, Copilot, etc.) will use this version instead of the extension's original.
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 · 21 lines · 11 tokens per session scan A fa5c348453ac
speckit.myext.myextcmd is a command published in the GitHub repository github/spec-kit (141,437 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 164 once invoked, about $0.0000 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 commands, from other repositories
book-internalize
A command that turns book-analysis reports into reusable writing guidance for a Novel Writer project. It creates style, structure, and rhythm configuration files that later writing commands can use.
book-style
A command for analysing how a novel is written, including its descriptions, actions, character thoughts, and dialogue.
stardust-session
A command for managing active sessions in a writing service called Stardust, including viewing their details and status. A session is a temporary workspace or connection used to carry out a task.
book-characters
A Chinese-language command for analysing how characters are created in a novel, including their traits, goals, relationships, and changes over the story. It expects the novel to be loaded first with the related analysis command.
book-formula
A command for extracting repeatable story structures from successful novels, such as opening hooks, chapter layouts, and plot escalation.
shizhangyu-foreshadow
A command for managing story foreshadowing, meaning clues planted early that become important later. It tracks objects, dialogue, events, and character clues through a novel.