performance

performance is a cursor rule for Cursor from lacymorrow/paperclip-hub. It costs 0 tokens per session (433 once invoked), scanned A, original, MIT.

A set of guidelines for making web applications load and respond efficiently. It covers page-speed measures, images, JavaScript, CSS, servers, browsers, and data loading.

In plain words
What is it for?
Use it when improving Core Web Vitals, reducing JavaScript and CSS size, optimising images, adding caching or lazy loading, and reviewing server or client performance.
Why use it?
It helps address slow pages, large downloads, delayed interaction, layout movement, and inefficient database or network requests.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when improving Core Web Vitals, reducing JavaScript and CSS size, optimising images, adding caching or lazy loading, and reviewing server or client performance.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/lacymorrow/paperclip-hub/performance
Install

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.

Clone the repo
git clone --depth 1 https://github.com/lacymorrow/paperclip-hub

Made for: Cursor.

Wrote 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.

agentmods badge for performance

README.md
[![agentmods](https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/performance/github.svg)](https://agentmods.dev/rules/lacymorrow/paperclip-hub/performance)
Your own site
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/performance"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/performance/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.

agentmods 80×15 button for performance

Your own site · 80×15
<a href="https://agentmods.dev/rules/lacymorrow/paperclip-hub/performance"><img src="https://agentmods.dev/badge/rules/lacymorrow/paperclip-hub/performance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 433 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00433
Opus 5.5 $0.00000 $0.00173
Sonnet 5.5 $0.00000 $0.00087
Haiku 4.5 $0.00000 $0.00043

Measured yesterday against content hash dd40b6105e71, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.cursor/rules/performance.mdc · 97 lines

What it actually says

Performance Best Practices

Core Web Vitals

  • Optimize LCP (Largest Contentful Paint)
  • Minimize FID (First Input Delay)
  • Reduce CLS (Cumulative Layout Shift)
  • Monitor Web Vitals
  • Set performance budgets
  • Regular performance audits
  • Document metrics

Image Optimization

  • Use next/image
  • Implement lazy loading
  • Choose proper formats
  • Optimize image sizes
  • Use responsive images
  • Implement caching
  • Monitor image performance

JavaScript

  • Implement code splitting
  • Use dynamic imports
  • Minimize bundle size
  • Tree shake unused code
  • Optimize dependencies
  • Use proper caching
  • Monitor JS performance

CSS

  • Minimize unused CSS
  • Use CSS modules
  • Implement critical CSS
  • Optimize tailwind usage
  • Reduce CSS bundle size
  • Use proper specificity
  • Monitor CSS performance

Server-Side

  • Use proper caching
  • Optimize database queries
  • Implement CDN
  • Use edge functions
  • Optimize API responses
  • Monitor server performance
  • Regular optimization

Client-Side

  • Implement proper caching
  • Use service workers
  • Optimize rendering
  • Reduce reflows/repaints
  • Handle offline support
  • Monitor client performance
  • Regular optimization

Data Loading

  • Use proper fetching
  • Implement caching
  • Handle loading states
  • Optimize payload size
  • Use proper protocols
  • Monitor data loading
  • Regular optimization

Build Optimization

  • Optimize build process
  • Minimize asset size
  • Use proper compression
  • Implement caching
  • Monitor build metrics
  • Regular build audits
  • Document optimizations

Monitoring

  • Use performance monitoring
  • Track key metrics
  • Set up alerts
  • Monitor trends
  • Regular analysis
  • Document findings
  • Take action on insights

Documentation

  • Document performance goals
  • Track improvements
  • Document optimizations
  • Keep metrics history
  • Regular reviews
  • Share best practices
  • Maintain documentation
Changes

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.

  1. yesterday First seen · 97 lines · 433 tokens per session scan A dd40b6105e71

Subscribe to this mod's changes

performance is a cursor rule published in the GitHub repository lacymorrow/paperclip-hub (15 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 433 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-11-10.

Related

performance compared with cursor rules from other repositories

performance next to 6 cursor rules from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
performancelacymorrow/paperclip-hubCursor rule15yesterdayMITA0Cursor
codex-premium-website-skillsTheGoat395/Codex-SkillsCursor rule13720d agoMITA0Cursor
componentss0vers/next-app-i18n-starterCursor rule664d agoMITA0Cursor
always-push-pritsmemeworks/adhxCursor rule195d agoMITA279Cursor
ui-design-systemkrivoox/agent-stack-templateCursor rule301mo agoMITA0Cursor
uiuseshape/ShapeCursor rule34yesterdaynoneA0Cursor
astro-development-guidelinesWebDevPeterGriffin/The-VibeCode-BibleCursor rule427d agononeA79Cursor