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/abderrahimghazali/cursor-rules/build-optimizationgit clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWhat 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.00617 |
| Opus 5 | $0.00000 | $0.00309 |
| Sonnet 5 | $0.00000 | $0.00123 |
| Haiku 4.5 | $0.00000 | $0.00062 |
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.
This is a copy
88% identical to build-optimization — 75 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Enhanced Build Process Optimization
Ensures optimal build configuration and process for better performance and maintainability.
actions:
-
type: enforce conditions:
-
pattern: "mode:\s*['"]development['"]" pattern_negate: "process\.env\.NODE_ENV === 'development'" message: "Set 'mode' to 'production' for production builds unless dynamically set by NODE_ENV."
-
pattern: "devtool:\s*['"]eval" message: "Use 'source-map' or 'hidden-source-map' for production builds to balance performance and debugging."
-
pattern: "optimization:\s*{[^}]?splitChunks:\s{[^}]?chunks:\s(?!'all')" message: "Enable code splitting for all chunks in optimization settings."
-
pattern: "optimization:\s*{[^}]?usedExports:\s(?!true)" message: "Enable tree shaking by setting 'usedExports' to true."
-
pattern: "output\s*:\s*{[^}]?filename:\s['"][^\[]+['"]" message: "Use content hashing in filenames for better caching (e.g., '[name].[contenthash].js')."
-
-
type: suggest message: | 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.
metadata: priority: high version: 1.1
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 · 57 lines · 0 tokens per session scan A d9be08565048
build-optimization is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 617 tokens. A static security scan graded it A with 0 findings. It is 88% identical to build-optimization, differing in 75 lines, and is treated as a copy.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.