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/thanhtung2693/specgate/using-specgategit clone --depth 1 https://github.com/thanhtung2693/specgateWhat 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.00115 | $0.00115 |
| Opus 5 | $0.00057 | $0.00057 |
| Sonnet 5 | $0.00023 | $0.00023 |
| Haiku 4.5 | $0.00012 | $0.00012 |
Grade A, and why
using-specgate 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.
What it actually says
Using SpecGate
A Git repository whose root contains .specgate/ is governed by SpecGate:
load one lifecycle phase before writing repository files. When the user
mentions SpecGate, load specgate. For lifecycle work, load exactly one setup,
preparation, or delivery phase before a write. Read-only concept and
troubleshooting questions stay in the root skill. Do not apply the SpecGate
lifecycle to generic specifications or work that is not tied to SpecGate.
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 · 14 lines · 115 tokens per session scan A 0dfde44af148
using-specgate is a cursor rule published in the GitHub repository thanhtung2693/specgate (5 stars, last pushed 11d ago), licensed Apache-2.0. It adds 115 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
cursor_rule_snippet
Latch decision-continuity gate for Cursor projects.
proxyshield-admin
ProxyShield admin UI conventions.
handoff
Export a Waybill Bundle by default, or import one when explicitly requested.
waybill
Alias for the Waybill handoff workflow.
agent-workspace
Repository evidence and validated engineering workflows.
example
Missing project/docs/does-not-exist.md. Also broken src/does-not-exist.ts.