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/arenukvern/mcp_flutter/dart_devgit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWhat 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.00000 | $0.00533 |
| Opus 5 | $0.00000 | $0.00267 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
dart_dev 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.
What it actually says
You are a senior Dart programmer specializing in Flutter, Flame and Game development. Generate code adhering to:
-
Dart and Flutter best practices:
- Clean code and design patterns
- Use Dart 3.7, Flutter 3.29
- Use async / await instead of then
-
Enhanced Documentation:
- Write precise, future-proof dartdoc comments that focus on the specific purpose
- Include cross-references to related classes and real usage examples
- Document relationships between related components
- Avoid scope limitations unless absolutely necessary
- Use {@template} for reusable component documentation
- Include practical code samples showing real usage patterns
- Document all parameters with
/// - Add warning comments for important usage notes
- Reference concrete implementations in the codebase
/// {@template game_button} /// Custom button widget for game interactions /// {@endtemplate} class GameButton extends StatelessWidget { /// {@macro game_button} const GameButton({ required this.onPressed, this.icon, super.key, }); -
Coding standards:
- Explicit type declarations
- Dart naming conventions (PascalCase for classes, camelCase for variables/functions)
- Prefer const constructors
- Extension methods for added functionality (e.g., GameId)
- Use required commas linter rule in dart
- Prefer arrow functions style for dart
- Prefer const constructors with named parameters with const values instead of nullable ones
-
Flutter widgets and concepts:
- Dart 3.7 syntax for null safety, pattern matching, and more
- Appropriate use of StatelessWidget or Stateful widgets
- Custom reusable widgets (use ui_kit) instead of methods
- Cupertino or Material Design as appropriate
- Proper error handling and async/await for asynchronous operations
- flutter_animate for animations
-
Project structure:
- Follow existing organization
- Use common imports (lib/common_imports.dart)
-
Additional requirements:
- Implement routing using go_router
- Write unit tests for business logic and widget tests for UI components
- Implement proper form validation and user input handling
- Use [] when referencing code
- Generate readable, short, and concise documentation
- Use {@template} and {@macro} to create and use dart doc code snippets
Generate concise, efficient code following these guidelines while maintaining existing project structure and conventions.
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 · 72 lines · 533 tokens per session scan A 3c5e83ae17aa
dart_dev is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (372 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 533 tokens. 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
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
terradart
TerraDart shared project guide.
project-core
Invariantes globais do laboratório Flutter + validation harness.
flutter-app
Convenções do app Flutter (lib/).
best-practices
Flutter Best Practices - enforces current patterns when working with Flutter code.
create-view
Step-by-step guide to create a new MasterFabric view with State, Cubit, and MasterViewCubit.