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/moritzmessner/flutter-cursor-rules/flutter_design_patternsgit clone --depth 1 https://github.com/MoritzMessner/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.00031 | $0.00673 |
| Opus 5 | $0.00015 | $0.00336 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
flutter_design_patterns 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.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎨 Design Patterns
1. Command Pattern
Purpose: Wrap async operations to handle loading, success, and error states automatically.
Use for: Async user actions, loading data, form submissions.
Implementation:
abstract class Command<T> extends ChangeNotifier {
Command();
bool _running = false;
bool get running => _running;
Result<T>? _result;
Result<T>? get result => _result;
bool get error => _result is Error;
bool get completed => _result is Ok;
void clearResult() { _result = null; notifyListeners(); }
}
class Command0<T> extends Command<T> {
Command0(this._action);
final Future<Result<T>> Function() _action;
Future<void> execute() async {
if (_running) return;
_running = true; _result = null; notifyListeners();
try { _result = await _action(); } finally { _running = false; notifyListeners(); }
}
}
class Command1<T, A> extends Command<T> {
Command1(this._action);
final Future<Result<T>> Function(A) _action;
Future<void> execute(A argument) async {
if (_running) return;
_running = true; _result = null; notifyListeners();
try { _result = await _action(argument); } finally { _running = false; notifyListeners(); }
}
}
2. Result Pattern
Purpose: Explicit error handling type.
Use for: Repository methods, potentially failing service methods.
Implementation:
sealed class Result<T> {
const Result();
factory Result.ok(T value) = Ok._;
factory Result.error(Exception error) = Error._;
}
final class Ok<T> extends Result<T> {
const Ok._(this.value);
final T value;
}
final class Error<T> extends Result<T> {
const Error._(this.error);
final Exception error;
}
3. Optimistic State Pattern
Purpose: Update UI immediately before server confirmation.
Use for: Likes, favorites, toggles.
Future<void> toggleFavorite(String id) async {
final wasFavorite = _favoriteIds.contains(id);
// Optimistically update
if (wasFavorite) _favoriteIds.remove(id); else _favoriteIds.add(id);
notifyListeners();
final result = await _repository.setFavorite(id, !wasFavorite);
// Rollback on failure
if (result is Error) {
if (wasFavorite) _favoriteIds.add(id); else _favoriteIds.remove(id);
notifyListeners();
// Show error...
}
}
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 · 105 lines · 673 tokens per session scan A 06a61e09ead0
flutter_design_patterns is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 673 once invoked, about $0.0002 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-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.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
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.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.