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/ratnesh-maurya/cursor-claude-personasWrote 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/ratnesh-maurya/cursor-claude-personas/rules-_sections)<a href="https://agentmods.dev/rules/ratnesh-maurya/cursor-claude-personas/rules-_sections"><img src="https://agentmods.dev/badge/rules/ratnesh-maurya/cursor-claude-personas/rules-_sections.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.00317 | $0.00317 |
| Opus 5 | $0.00159 | $0.00159 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
rules--_sections 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 4d 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
Sections
This file defines all sections, their ordering, impact levels, and descriptions. The section ID (in parentheses) is the filename prefix used to group rules.
1. Eliminating Waterfalls (async)
Impact: CRITICAL
Description: Waterfalls are the #1 performance killer. Each sequential await adds full network latency. Eliminating them yields the largest gains.
2. Bundle Size Optimization (bundle)
Impact: CRITICAL
Description: Reducing initial bundle size improves Time to Interactive and Largest Contentful Paint.
3. Server-Side Performance (server)
Impact: HIGH
Description: Optimizing server-side rendering and data fetching eliminates server-side waterfalls and reduces response times.
4. Client-Side Data Fetching (client)
Impact: MEDIUM-HIGH
Description: Automatic deduplication and efficient data fetching patterns reduce redundant network requests.
5. Re-render Optimization (rerender)
Impact: MEDIUM
Description: Reducing unnecessary re-renders minimizes wasted computation and improves UI responsiveness.
6. Rendering Performance (rendering)
Impact: MEDIUM
Description: Optimizing the rendering process reduces the work the browser needs to do.
7. JavaScript Performance (js)
Impact: LOW-MEDIUM
Description: Micro-optimizations for hot paths can add up to meaningful improvements.
8. Advanced Patterns (advanced)
Impact: LOW
Description: Advanced patterns for specific cases that require careful implementation.
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.
- 4d ago First seen · 47 lines · 317 tokens per session scan A 01c59969e4e8
rules--_sections is a cursor rule published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It adds 317 tokens to every session, about $0.0016 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-09-03.
Other cursor rules, from other repositories
reqforge-dev-build
Dev Builder — implementation execution. Build code phase by phase following DEV-PLAN, each Task goes through review → fix loop.
mena-payment-guardian
Use when building or reviewing Arab/MENA payment or BNPL flows with Paymob, FawryPay, Geidea, PayTabs, Tap Payments, MyFatoorah, HyperPay, Moyasar, Amazon Payment Services, EasyKash, Kashier, PaySky, Tabby, Tamara, valU, Souhoola, callbacks, webhooks, HMAC, SecureHash, redirects, refunds, captures, or payment secrets.
execution
Repository execution and verification commands.
tell-domain-research
Auto-trigger website domain research before any new site build.
research-before-suggesting
Never make up features, APIs, or config options. Research before suggesting technical solutions.
github-repo-triage
Triage and maintain GitHub repos — issues, PRs, cherry-picks, releases, publishing.