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/saif-shines/technical-writing-cursor-rulesWrote 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/saif-shines/technical-writing-cursor-rules/test-rule)<a href="https://agentmods.dev/rules/saif-shines/technical-writing-cursor-rules/test-rule"><img src="https://agentmods.dev/badge/rules/saif-shines/technical-writing-cursor-rules/test-rule.svg" alt="Measured on agentmods" 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.00000 | $0.00030 |
| Opus 5 | $0.00000 | $0.00015 |
| Sonnet 5 | $0.00000 | $0.00006 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
test-rule 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 7d 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
Test Rule
This is a test rule that demonstrates the proper format for Cursor rules.
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.
- 7d ago First seen · 9 lines · 0 tokens per session scan A 6d49c6b4965e
test-rule is a cursor rule published in the GitHub repository saif-shines/technical-writing-cursor-rules (7 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 30 tokens. 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.
monitoring
Monitoring, observability, and alerting rules.
documentation-standards
Documentation standards for code, APIs, and architecture.
token-efficiency
Token optimization rules to reduce AI costs by 30%+.
performance
Frontend performance optimization rules. Apply when optimizing UI or bundle.
data-fetching
Data fetching patterns with TanStack Query, Server Components, and Supabase.