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 skills add reza00farjam/flutter-mvvm-architecture-skill --skill flutter-mvvm-architecturegit clone --depth 1 https://github.com/reza00farjam/flutter-mvvm-architecture-skillWrote 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/skills/reza00farjam/flutter-mvvm-architecture-skill/flutter-mvvm-architecture)<a href="https://agentmods.dev/skills/reza00farjam/flutter-mvvm-architecture-skill/flutter-mvvm-architecture"><img src="https://agentmods.dev/badge/skills/reza00farjam/flutter-mvvm-architecture-skill/flutter-mvvm-architecture/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/reza00farjam/flutter-mvvm-architecture-skill/flutter-mvvm-architecture"><img src="https://agentmods.dev/badge/skills/reza00farjam/flutter-mvvm-architecture-skill/flutter-mvvm-architecture.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00175 | $0.03277 |
| Opus 5 | $0.00088 | $0.01639 |
| Sonnet 5 | $0.00035 | $0.00655 |
| Haiku 4.5 | $0.00017 | $0.00328 |
Grade A, and why
flutter-mvvm-architecture 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 12d 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter MVVM Architecture
This skill encodes the Flutter team's official recommended app architecture:
https://docs.flutter.dev/app-architecture, including the
core architecture concepts
(separation of concerns, single source of truth, unidirectional data flow,
immutable state) summarized under "Core principles" below. It's the same
architecture used in Flutter's reference sample, the
Compass app.
Apply it by default whenever generating or reviewing non-trivial Flutter code
(more than a single throwaway widget). These are the Flutter team's
recommendations, not rigid law — treat them as strong defaults, and adapt
when a repo already has an established, different convention (e.g. it's
already fully built on riverpod or flutter_bloc). Even then, keep the
underlying principles: separation of concerns, single source of truth,
unidirectional data flow, and dumb widgets.
Verified against the live docs on 2026-08-14 (site showed Flutter 3.44.7, pages last updated May–July 2026). If
provider,go_router, orfreezedship a breaking major version, or docs.flutter.dev/app-architecture shows a materially newer revision, re-check that page before trusting the package-specific code samples in this skill.
Why this matters
Good architecture makes Flutter apps easier to maintain, test, and scale
across a growing team, and it's what most production Flutter codebases
converge on. Code that mixes network calls, business logic, and widget code
in one StatefulWidget works for a demo but rapidly becomes unmaintainable
and untestable. Defaulting to this layered structure avoids that outcome
without meaningfully slowing down simple requests.
Core principles (always apply, regardless of feature size)
- Separation of concerns. Split the app into a UI layer and a data layer (plus an optional domain layer). Layers may only talk to the layer directly above or below them — the UI layer never touches the data layer directly, and vice versa.
- Single source of truth (SSOT). Every type of data has exactly one owner: a Repository. If data can change, the repository is the only class allowed to change it.
- Unidirectional data flow (UDF). User events flow UI → logic → data. New state flows data → logic → UI. Data never mutates in place inside a widget or view model.
- UI is a function of (immutable) state. Widgets render, they don't decide. Data should be immutable; when it changes, a new instance is created and the UI rebuilds in response.
- Widgets stay dumb. A widget/View should hold as little logic as possible — see the exact allowed list under Views below.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 251 lines · 175 tokens per session scan A be65ff1087af
flutter-mvvm-architecture is a skill published in the GitHub repository reza00farjam/flutter-mvvm-architecture-skill (1 stars, last pushed 28d ago), licensed MIT. It adds 175 tokens to every session and 3,277 once invoked, about $0.0009 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 skills, from other repositories
flutter-bloc-development
Build Flutter features using BLoC state management, clean architecture layers, and the project's design system. Apply when creating screens, widgets, or data integrations.
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
android-navigation-3
Install and migrate to Jetpack Navigation 3. Use when implementing Navigation 3 patterns including NavDisplay, NavKey routes, deep links, multiple backstacks, scenes (dialogs, bottom sheets), or migrating from Navigation 2.
firebase-app-check
Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.