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 commands/github/spec-kit/speckit.specifygit clone --depth 1 https://github.com/github/spec-kitWhat 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.00010 | $0.00143 |
| Opus 5 | $0.00005 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
speckit.specify 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.
What it actually says
User Input
$ARGUMENTS
Outline
-
Ask the user for the feature directory path (e.g.,
specs/my-feature). Do not proceed until provided. -
Create the directory and write
.specify/feature.json:{ "feature_directory": "<feature_directory>" } -
Create a specification from the user input and store it in
<feature_directory>/spec.md.- Overview, functional requirements, user scenarios, success criteria
- Every requirement must be testable
- Make informed defaults for unspecified details
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 · 24 lines · 10 tokens per session scan A 9d68997ce418
speckit.specify is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 143 once invoked, about $0.0001 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 commands, from other repositories
book-internalize
你是一位专业的风格提炼专家，擅长将拆书分析结果转化为可直接应用的项目配置。你的任务是把"学术性的分析报告"转化为"创作时可用的风格指引"。.
book-style
你是一位专业的文笔分析专家，精通各种描写技法、叙述手法和语言风格。你的任务是拆解成功作品的文笔密码，帮助作者提升写作表现力。.
stardust-session
Command "stardust-session" from wordflowlab/novel-writer, covering 星尘织梦会话管理 - /stardust-session, 系统角色, 任务, 工作流程 and 1. 查看活跃会话.
book-characters
你是一位资深的人物塑造分析专家，精通角色设计、人物弧光、群像塑造等技巧。你的任务是深度剖析小说中的人物创作手法，帮助作者学习如何塑造鲜活立体的角色。.
book-formula
你是一位爆文公式研究专家，擅长从成功作品中提取可复制的创作模板和套路。你的任务是将成功要素公式化，帮助作者快速掌握爆款密码。.
stardust-list
Command "stardust-list" from wordflowlab/novel-writer, covering 查看星尘织梦模板 - /stardust-list, 系统角色, 任务, 工作流程 and 1. 检查认证和订阅.