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/girijashankarj/cursor-handbook/performancegit clone --depth 1 https://github.com/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/performance)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/performance"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/performance.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 | $0.00000 | $0.00462 |
| Opus 5 | $0.00000 | $0.00231 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
performance 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
Frontend Performance Rules
Core Web Vitals Targets
| Metric | Target | Description |
|---|---|---|
| LCP | <2.5s | Largest Contentful Paint |
| FID/INP | <100ms | First Input Delay / Interaction to Next Paint |
| CLS | <0.1 | Cumulative Layout Shift |
| TTFB | <800ms | Time to First Byte |
Loading Performance
- Code split routes with
React.lazy()or dynamicimport() - Preload critical resources: fonts, above-the-fold images
- Use
loading="lazy"for below-the-fold images - Implement skeleton screens instead of spinners
- Set explicit dimensions on images and embeds to prevent CLS
- Use responsive images with
srcsetandsizes
Bundle Optimization
- Maximum initial bundle size: 200KB (gzipped)
- Analyze bundle with webpack-bundle-analyzer or equivalent
- Tree-shake unused exports
- Externalize large libraries to CDN when appropriate
- Use dynamic imports for heavy components (charts, editors, maps)
Runtime Performance
- Virtualize long lists (>100 items) — use react-window or react-virtuoso
- Debounce search inputs (300ms), throttle scroll/resize handlers (16ms)
- Use
requestAnimationFramefor smooth animations - Avoid layout thrashing — batch DOM reads and writes
- Use Web Workers for CPU-intensive operations
Caching Strategy
- Service Worker for offline support and asset caching
- Cache API responses with appropriate TTL
- Use
stale-while-revalidatepattern for non-critical data - Implement HTTP caching headers:
Cache-Control,ETag,Last-Modified - Use CDN for static assets
Monitoring
- Track Core Web Vitals in production (via web-vitals library)
- Set up performance budgets in CI
- Alert on performance regressions
- Monitor third-party script impact
- Review Lighthouse scores monthly
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 · 52 lines · 0 tokens per session scan A 4bd8df37402e
performance is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (30 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 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-09-03.
Other cursor rules, from other repositories
web
Web build conventions (separate from native and RN JS).
components
Component patterns and UI conventions.
html-css
Rules for HTML, CSS, and styling files.
react
Rules for React component files (any framework).
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
cursorrules
Use functional components in React. Prefer Tailwind CSS classes.