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/ZanzyTHEbar/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/zanzythebar/cursor-rules/sample_cursor_rule)<a href="https://agentmods.dev/rules/zanzythebar/cursor-rules/sample_cursor_rule"><img src="https://agentmods.dev/badge/rules/zanzythebar/cursor-rules/sample_cursor_rule/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/zanzythebar/cursor-rules/sample_cursor_rule"><img src="https://agentmods.dev/badge/rules/zanzythebar/cursor-rules/sample_cursor_rule.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.00088 | $0.00088 |
| Opus 5.5 | $0.00035 | $0.00035 |
| Sonnet 5.5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
sample_cursor_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 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
React Component Guidelines
Use functional components with hooks. Prefer composition over inheritance. Always add PropTypes or TypeScript interfaces.
Naming Conventions
- PascalCase for component names
- camelCase for props and handlers
- Prefix event handlers with "handle"
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 · 19 lines · 88 tokens per session scan A 4acfe97404cb
sample_cursor_rule is a cursor rule published in the GitHub repository ZanzyTHEbar/cursor-rules (3 stars, last pushed 6mo ago), licensed MIT. It adds 88 tokens to every session, about $0.0004 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
nextjs
Rules for Next.js projects (App Router and Pages Router).
react
Rules for React component files (any framework).
tanstack-query
TanStack Query / React Query: query keys, mutations, caching, optimistic updates.
expo
Expo/React Native: native modules, navigation, platform-specific code.
react
React: hooks, composition, performance patterns.
t3-stack
T3 Stack: tRPC + Prisma + NextAuth integration patterns.