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_architecture_overviewgit 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.00029 | $0.01030 |
| Opus 5 | $0.00015 | $0.00515 |
| Sonnet 5 | $0.00006 | $0.00206 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
flutter_architecture_overview 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🏗️ Architecture Overview
Three-Layer Architecture
┌─────────────────────────────────────────┐
│ UI LAYER (Presentation) │
│ Views (Widgets) + ViewModels │
│ - User interface │
│ - User interaction handling │
│ - UI state management │
└─────────────────────────────────────────┘
↓↑
┌─────────────────────────────────────────┐
│ DOMAIN LAYER (Business Logic) │
│ Models + Use Cases │
│ - Business logic │
│ - Domain models │
│ - Application rules │
└─────────────────────────────────────────┘
↓↑
┌─────────────────────────────────────────┐
│ DATA LAYER (Data Access) │
│ Repositories + Services │
│ - Data fetching │
│ - Data caching │
│ - External APIs │
└─────────────────────────────────────────┘
Key Principles
- Separation of Concerns: Each layer has a distinct responsibility
- Dependency Rule: Dependencies point inward (UI → Domain → Data)
- Testability: Each layer can be tested independently
- Scalability: Easy to add features without breaking existing code
- Maintainability: Clear structure makes code easy to navigate and modify
📁 Project Structure
Required Directory Layout
lib/
├── ui/ # UI LAYER
│ ├── core/
│ │ ├── ui/ # Shared widgets & components
│ │ ├── themes/ # Theme definitions & styling
│ │ └── view_model/ # Base/core view models
│ └── <feature>/ # Feature-specific UI modules
│ ├── view_model/ # Feature ViewModels
│ │ └── <feature>_view_model.dart
│ └── widgets/ # Feature screens & widgets
│ └── <feature>_screen.dart
│
├── domain/ # DOMAIN LAYER
│ └── models/ # Pure business models
│ └── <model_name>.dart
│
├── data/ # DATA LAYER
│ ├── models/ # API/Data models
│ │ ├── <model_name>_dto.dart # Data transfer objects
│ │ └── responses/ # API response wrappers
│ ├── repositories/ # Data repositories
│ │ └── <feature>_repository.dart
│ └── services/ # Application services
│ └── <service_name>_service.dart
│
├── utils/ # Shared utilities
│ ├── command/ # Command pattern classes
│ └── result/ # Result pattern classes
│
├── routing/ # Navigation & routing
└── main.dart # App entry point
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.
- 2d ago First seen · 115 lines · 29 tokens per session scan A d468f73ab9ba
flutter_architecture_overview is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,030 once invoked, about $0.0001 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.