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/jaansokk/cursor_toolsWrote 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/jaansokk/cursor_tools/include-specs)<a href="https://agentmods.dev/rules/jaansokk/cursor_tools/include-specs"><img src="https://agentmods.dev/badge/rules/jaansokk/cursor_tools/include-specs/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/jaansokk/cursor_tools/include-specs"><img src="https://agentmods.dev/badge/rules/jaansokk/cursor_tools/include-specs.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.00057 | $0.00057 |
| Opus 5.5 | $0.00023 | $0.00023 |
| Sonnet 5.5 | $0.00011 | $0.00011 |
| Haiku 4.5 | $0.00006 | $0.00006 |
Grade A, and why
include-specs 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.
What it actually says
Use _specs/spec-index.md to decide which spec(s) apply to the current task.
Only consult/include the spec(s) referenced there that are relevant to the prompt at hand.
Specs are the source of truth for scope and acceptance criteria.
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 · 6 lines · 57 tokens per session scan A 252121b64b20
include-specs is a cursor rule published in the GitHub repository jaansokk/cursor_tools (1 stars, last pushed 7mo ago), licensed MIT. It adds 57 tokens to every session, about $0.0002 per session on Opus 5.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
app-router-patterns
Next.js 14+ App Router patterns — Server Components, Client Components, Route Handlers, Server Actions, and metadata API.
test-patterns
Selenium pytest test patterns — data-driven tests, fixtures, error handling, and performance checks.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.
components
Component patterns and UI conventions.
git
Git workflow and commit conventions.