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/ivangrynenko/cursorrules/build-optimizationgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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.00578 |
| Opus 5 | $0.00000 | $0.00289 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
build-optimization 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- build-optimization — 88% identical, 75 lines differ
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced Build Process Optimization
Ensures optimal build configuration and process for better performance and maintainability.
Rule Details
-
Name: enhanced_build_optimization
-
Description: Enforce standards for optimizing build processes
Filters
- file extension pattern:
"\\.(js|ts|json)$" # Expanded to cover more config file types
Enforcement Checks
- Conditions:
- pattern
mode:\\s*['\"]development['\"]– negatedprocess\\.env\\.NODE_ENV === 'development'– Set 'mode' to 'production' for production builds unless dynamically set by NODE_ENV. - pattern
devtool:\\s*['\"]eval– Use 'source-map' or 'hidden-source-map' for production builds to balance performance and debugging. - pattern
optimization:\\s*{[^}]*?splitChunks:\\s*{[^}]*?chunks:\\s*(?!'all')– Enable code splitting for all chunks in optimization settings. - pattern
optimization:\\s*{[^}]*?usedExports:\\s*(?!true)– Enable tree shaking by setting 'usedExports' to true. - pattern
output\\s*:\\s*{[^}]*?filename:\\s*['\"][^\\[]+['\"]– Use content hashing in filenames for better caching (e.g., '[name].[contenthash].js').
- pattern
Suggestions
- Guidance: Build Optimization Best Practices:
- Code Splitting: Implement code splitting to load only what's necessary for each page or component.
- Tree Shaking: Enable tree shaking to eliminate dead code, which reduces bundle size.
- Asset Optimization:
- Compress images and use modern formats like WebP where supported.
- Use lazy loading for images and other media.
- Caching:
- Configure proper caching strategies (e.g., HTTP headers, service workers for PWA).
- Use long-term caching for static assets with content hashing in filenames.
- Modern JavaScript:
- Use ES6+ features but ensure polyfills for older browsers if needed.
- Consider using features like module/nomodule for graceful degradation.
- Minification & Compression: Ensure all JavaScript and CSS are minified and consider enabling gzip compression on the server.
- Performance Budgets: Set performance budgets to keep bundle sizes in check.
- Environment Variables: Use environment variables for configuration differentiation between development and production.
- CI/CD: Integrate with CI/CD pipelines for automated builds and testing, ensuring only optimized code goes to production.
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 · 48 lines · 0 tokens per session scan A b7a379ab7148
build-optimization is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 578 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-30.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.