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 rules/snowdreamtech/template/speckit_speckit.git.validategit 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.00065 | $0.00065 |
| Opus 5 | $0.00032 | $0.00032 |
| Sonnet 5 | $0.00013 | $0.00013 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
speckit_speckit.git.validate 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
Speckit Workflow: speckit.git.validate
When the user asks to run /speckit.git.validate, you MUST read .specify/commands/speckit.git.validate.md and follow 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 · 9 lines · 65 tokens per session scan A 72f7bc28512a
speckit_speckit.git.validate is a cursor rule published in the GitHub repository snowdreamtech/template (15 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session, about $0.0003 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 cursor rules, from other repositories
agent-routing.pi-input-intercept
Codex 模型經 Pi machine dispatch 提出問題時的攔截、評估、代答或升級 protocol；觸及 spectra change / screenshot 情境時 path-scoped 載入.
auth-data-path-consistency
Auth 策略與資料存取路徑一致性——防止混合 auth 狀態導致 silent 權限降級.
vk-org-resolution
VirtualKey org resolution has TWO join chains (Project for application VKs, Owner for personal VKs); vkSelectSQL must COALESCE both or personal VKs silently return NULL org.
design-tokens
Visual values via CSS variables; no hex / rgb literals in style.
agent-routing.pi-watch-protocol
Pi 派工的標準流程模板、Pi Watch Protocol、Plan-first / Git baseline declaration、$spectra-apply Runtime Gate、screenshot-review verify mode 派工與監看、配額耗盡的 fallback 鏈全文、Spectra Propose / Apply 的 dispatch 契約、Orchestration Residency 的四步做法、Routing Table 下推列（spectra 三列 + screenshot 兩列）的取證全文；apply 階段 / 觸及 spectra change 時 path-scoped…
i18n-mandatory
All user-visible UI text uses t('namespace:section.key') from react-i18next.