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/snowdreamtech/templateWrote 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/rules/snowdreamtech/template/speckit_speckit.git.validate)<a href="https://agentmods.dev/rules/snowdreamtech/template/speckit_speckit.git.validate"><img src="https://agentmods.dev/badge/rules/snowdreamtech/template/speckit_speckit.git.validate/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/rules/snowdreamtech/template/speckit_speckit.git.validate"><img src="https://agentmods.dev/badge/rules/snowdreamtech/template/speckit_speckit.git.validate.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.00065 | $0.00065 |
| Opus 5.5 | $0.00026 | $0.00026 |
| Sonnet 5.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 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.
This is a copy
100% identical to speckit_speckit.git.validate — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 1mo ago 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 (16 stars, last pushed 4d ago), licensed MIT. It adds 65 tokens to every session, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to speckit_speckit.git.validate, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
release-compat-policy
1.0 GA — backward compatibility for shipped contracts; greenfield for internal-only code.
worktree-per-session
Each parallel Claude Code / Cursor session runs in its own git worktree under ./worktrees/.
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.