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/app_architecture.guidegit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/app_architecture.guide)<a href="https://agentmods.dev/rules/arenukvern/mcp_flutter/app_architecture.guide"><img src="https://agentmods.dev/badge/rules/arenukvern/mcp_flutter/app_architecture.guide.svg" alt="Measured on agentmods" 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 | $0.01035 | $0.01035 |
| Opus 5 | $0.00517 | $0.00517 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
app_architecture.guide 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 3d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Architecture Overview
This document provides a condensed, unified overview of the application's architecture. It is designed to be a primary reference for understanding the core concepts, structure, and development patterns.
1. High-Level Architecture & Directory Structure
The application follows a standard layered architecture, separating concerns into distinct layers and directories.
lib/
├── core/ # Core abstractions & shared utilities
├── components/ # Shared UI components in atom design style. See
├── data_models/ # Immutable data models based on extension types. See `[dart_extension_type_const_models.mdc](mdc:.cursor/rules/dart_extension_type_const_models.mdc)` for more details.
├── data_resources/ # UI state holders (Resources) See `[command_resource_pattern.guide.mdc](mdc:.cursor/rules/command_resource_pattern.guide.mdc)` for more details.
├── data_commands/ # Logic to update Resources (Commands) See `[command_resource_pattern.guide.mdc](mdc:.cursor/rules/command_resource_pattern.guide.mdc)` for more details.
├── data_api/ # Data access layer (file I/O, parsing)
├── data_services/ # Data services (file I/O, parsing)
├── mechanics/ # Mechanics (game mechanics)
├── di/ # Dependency injection setup See `[di_usage.guide.mdc](mdc:.cursor/rules/di_usage.guide.mdc)` for more details.
├── services/ # Isolated Application-level business logic
├── {ui_domain}/ # Domain or Feature-specific screens and widgets, like ui_vitamin_selection, ui_info etc..
├── theme/ # Context based Theme
└── main.dart # Application entry point
- Data Layer:
data_models/&data_api/handle the representation of and interaction with the data. - State & Service Layer:
data_resources/&data_commands/&data_services/manage application state and orchestrate business logic. - UI Layer:
{ui_domain}/contains all Flutter widgets, organized by domain and then by feature.
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.
- 3d ago First seen · 76 lines · 1,035 tokens per session scan A 7d2acbdd98be
app_architecture.guide is a cursor rule published in the GitHub repository Arenukvern/mcp_flutter (373 stars, last pushed 8d ago), licensed MIT. It adds 1,035 tokens to every session, about $0.0052 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
terradart
TerraDart shared project guide.
validation-harness
Validation harness — interfaces, adapters, cenários E2E.
project-core
Invariantes globais do laboratório Flutter + validation harness.
flutter-app
Convenções do app Flutter (lib/).
testing
Cursor rule "testing" from BlackLeg15/desafio_bloc_1, covering testing and cobertura existente.
best-practices
Flutter Best Practices - enforces current patterns when working with Flutter code.