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.
git clone --depth 1 https://github.com/MoritzMessner/flutter-cursor-rulesWrote 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/moritzmessner/flutter-cursor-rules/flutter_best_practices)<a href="https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_best_practices"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/flutter_best_practices/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.
<a href="https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_best_practices"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/flutter_best_practices.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.00497 |
| Opus 5.5 | $0.00009 | $0.00199 |
| Sonnet 5.5 | $0.00005 | $0.00099 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
flutter_best_practices 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 2mo ago.
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
✅ Best Practices
DO's
- ✅ Use Result for all operations that can fail.
- ✅ Wrap async operations in Commands to handle loading/error states.
- ✅ Keep views simple; delegate logic to ViewModels.
- ✅ Use private fields with public getters in ViewModels to protect state.
- ✅ Call notifyListeners() after state changes in ViewModels.
- ✅ Handle all error cases explicitly (e.g., using switch on Result).
- ✅ Use const constructors for widgets and models where possible.
- ✅ Dispose ViewModels and streams when no longer needed.
- ✅ Use Code Generation for models (
freezed) and serialization (json_serializable) to reduce boilerplate and ensure type safety.
DON'Ts
- ❌ Don't put business logic in views.
- ❌ Don't call repositories directly from views; go through the ViewModel.
- ❌ Don't import UI code in ViewModels (no
flutter/material.dartunless absolutely necessary for non-UI types, but generally avoid). - ❌ Don't throw exceptions in repositories; return
Result.errorinstead. - ❌ Don't forget to handle loading states in the UI.
- ❌ Don't use StatefulWidget if the state can be managed by the ViewModel (unless it's purely ephemeral UI state like animation controllers).
- ❌ Don't create ViewModels inside
buildmethod.
💡 Tips for Success
- Start Simple: Don't over-engineer.
- Be Consistent: Stick to the patterns (Command, Result, MVVM).
- Write Tests: Catch violations early.
- Refactor Incrementally: Don't try to fix everything at once.
- Focus on Value: Architecture supports the product.
🔄 Migration Guide (Summary)
- Extract Data Layer: Create repositories, move API calls there.
- Implement Patterns: Add Command/Result patterns.
- Refine ViewModels: Move logic from Views to ViewModels.
- Clean Up Models: Separate Domain vs Data (DTO) models.
- Add Tests: Verify behavior.
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.
- 2mo ago First seen · 44 lines · 23 tokens per session scan A 7c82b1264703
flutter_best_practices is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 21d ago), licensed MIT. It adds 23 tokens to every session and 497 once invoked, about $0.0001 per session on Opus 5.5. 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-31.
Other cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
nativescript
NativeScript best practices and patterns for mobile applications.
gradle
Enforce modern Gradle build practices for Java and Android projects, focusing on Kotlin DSL, modularity, version catalogs, and performance optimizations.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.