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/snowdreamtech/template/speckit.taskstoissuesgit clone --depth 1 https://github.com/snowdreamtech/templateWhat 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.00009 | $0.00040 |
| Opus 5 | $0.00005 | $0.00020 |
| Sonnet 5 | $0.00002 | $0.00008 |
| Haiku 4.5 | $0.00001 | $0.00004 |
Grade A, and why
speckit.taskstoissues 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 today.
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
Execute Command
Please read .specify/commands/speckit.taskstoissues.md and execute its instructions exactly.
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.
- today First seen · 8 lines · 9 tokens per session scan A 0ecc9f7ec9e6
speckit.taskstoissues is a command published in the GitHub repository snowdreamtech/template (15 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 40 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
review-feature
Review a KMP feature against architecture patterns and spec.
health-report
Show health status for all feature modules.
recover
Scan orphaned worktrees and stale branches, then offer explicit approval-gated cleanup.
capture
Triage raw inbox notes into reviewed repository destinations without deleting their sources.
content-shipped
Log a completed piece of content to content/log.md after the user confirms it was published.
bump-template-version
Bumps the template repository's own internal version — the version tracked in .template/CHANGELOG-TEMPLATE.md's link footer. This is the SOLE place where the template's version lives, by design — VERSION, CHANGELOG.md, Cargo.toml [workspace.package].version, and the README.md version badge are all kept free of any…