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/ricardocaste/flutter-cursor-rules/cursorrulesgit clone --depth 1 https://github.com/ricardocaste/flutter-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.00589 | $0.00589 |
| Opus 5 | $0.00295 | $0.00295 |
| Sonnet 5 | $0.00118 | $0.00118 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
cursorrules 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 flutter-app-expert-cursorrules-prompt-file — 50 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
// Flutter App Expert .cursorrules
// Flexibility Notice
// Note: This is a recommended project structure, but be flexible and adapt to existing project structures. // Do not enforce these structural patterns if the project follows a different organization. // Focus on maintaining consistency with the existing project architecture while applying Flutter best practices.
// Flutter Best Practices
const flutterBestPractices = [ "Adapt to existing project architecture while maintaining clean code principles", "Use Flutter 3.x features and Material 3 design", "Implement clean architecture with BLoC pattern, in particular with Cubit", "Follow proper state management principles", "Use proper dependency injection", "Implement proper error handling", "Follow platform-specific design guidelines", "Use proper localization techniques", ];
// Project Structure
// Note: This is a reference structure. Adapt to the project's existing organization
const projectStructure = lib/ data/ datasources/ models/ providers/ repositories/ firebase_options.dart domain/ entities/ repositories/ usecases/ infrastructure/ constants/ di/ errir/ extensions/ network/ services/ usecases/ utils.dart presentation/ bloc/ nav/ pages/ widgets/ themes.dart main.dart test/ unit/ widget/ integration/;
// Coding Guidelines
const codingGuidelines = `
- Use proper null safety practices
- Implement proper error handling with Either type
- Follow proper naming conventions
- Use proper widget composition
- Implement proper routing using GoRouter
- Use proper form validation
- Follow proper state management with BLoC, in particular with Cubit
- Implement proper dependency injection using GetIt
- Use proper asset management
- Follow proper testing practices `;
// Widget Guidelines
const widgetGuidelines = `
- Keep widgets small and focused
- Use const constructors when possible
- Implement proper widget keys
- Follow proper layout principles
- Use proper widget lifecycle methods
- Implement proper error boundaries
- Use proper performance optimization techniques
- Follow proper accessibility guidelines `;
// Performance Guidelines
const performanceGuidelines = `
- Use proper image caching
- Implement proper list view optimization
- Use proper build methods optimization
- Follow proper state management patterns
- Implement proper memory management
- Use proper platform channels when needed
- Follow proper compilation optimization techniques `;
// Testing Guidelines
const testingTestingGuidelines = `
- Write unit tests for business logic
- Implement widget tests for UI components
- Use integration tests for feature testing
- Implement proper mocking strategies
- Use proper test coverage tools
- Follow proper test naming conventions
- Implement proper CI/CD testing `;
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 · 111 lines · 589 tokens per session scan A 992032ec331d
cursorrules is a cursor rule published in the GitHub repository ricardocaste/flutter-cursor-rules (3 stars, last pushed 1y ago), licensed Apache-2.0. It adds 589 tokens to every session, about $0.0029 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to flutter-app-expert-cursorrules-prompt-file, differing in 50 lines, and is treated as a copy.
Other cursor rules, from other repositories
appstore-ppp-pricing
Bulk-set App Store in-app purchase and subscription prices across 175+ countries by purchasing power parity (PPP) with the appstore-ppp-prices CLI. Use for regional App Store pricing, price localization, bulk price updates, or making an app cheaper in emerging markets.
web-nodejs-i18n
Keep web-nodejs console i18n keys in sync across all locale files.
i1n
This project uses i1n for managing translations.
cursorrules
You are an expert React Native developer working in a production-grade Expo template. Follow every rule below exactly. When in doubt, look at an existing file and match its patterns.
mobile-i18n-standards
Mobile i18n standards for all user-facing text.
kotlin
Android finance precision, RTL/i18n, and Kotlin AI skill rules.