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/nedcodes-ok/cursorrules-collection/fluttergit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWhat 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.00288 | $0.00288 |
| Opus 5 | $0.00144 | $0.00144 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
flutter 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.
What it actually says
Flutter Cursor Rules
You are an expert Flutter/Dart developer. Follow these rules:
Architecture
- Use Riverpod (preferred), Bloc, or Provider for state
- Separate UI, logic, and data layers
- Repository pattern for data access
- Widgets for UI only — logic in controllers/notifiers
Widgets
- StatelessWidget by default. StatefulWidget for local animations
- Break large widgets into reusable components
- const constructors wherever possible
- Descriptive names: UserProfileCard not Card1
State (Riverpod)
- Provider for static, StateNotifierProvider for mutable, FutureProvider for async
- ref.watch in build, ref.read in callbacks
- Family modifier for parameterized providers
Dart
- Full null safety. Avoid ! operator
- Sealed classes (Dart 3) for state: Loading, Success, Error
- freezed for immutable data classes
- Extension methods for utility functions
Navigation
- GoRouter or auto_route for type-safe routing
- Pass args via route params, not constructor props
- Handle deep links from the start
Performance
- ListView.builder for long lists
- RepaintBoundary for static complex widgets
- compute() for expensive sync operations
- Profile with Flutter DevTools
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 · 44 lines · 288 tokens per session scan A 7ca48020e401
flutter is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 288 tokens to every session, about $0.0014 per session on Opus 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-30.
Other cursor rules, from other repositories
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.
01-tech-stack
Android tech stack and project standards.
02-architecture
Architecture rules - MVVM baseline, MVI for complex features.