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/implementgit 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.00014 | $0.03140 |
| Opus 5 | $0.00007 | $0.01570 |
| Sonnet 5 | $0.00003 | $0.00628 |
| Haiku 4.5 | $0.00001 | $0.00314 |
Grade A, and why
implement 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 yesterday.
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.implement — 91% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before implementation):
- Check if
.specify/extensions.ymlexists in the project root. - If it exists, read it and look for entries under the
hooks.before_implementkey - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- For each executable hook, output the following based on its
optionalflag:- Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` - Mandatory hook (
optional: false):
After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.{command}id shown above, e.g. a skills-mode agent runs it as/skill:speckit-...or$speckit-...). Emitting the block alone does not run the hook.
- Optional hook (
- If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
Outline
- Run
{SCRIPT}from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot").
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.
- yesterday First seen · 223 lines · 14 tokens per session scan A d70c8b66470c
implement is a command published in the GitHub repository github/spec-kit (132,298 stars, last pushed 3d ago), licensed MIT. It adds 14 tokens to every session and 3,140 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. 检查认证和订阅.