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 skills/yendangn/flutter-app-builder/flutter-architecturenpx skills add yendangn/flutter-app-builder --skill flutter-architecturegit clone --depth 1 https://github.com/yendangn/flutter-app-builderWrote 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/yendangn/flutter-app-builder/flutter-architecture)<a href="https://agentmods.dev/skills/yendangn/flutter-app-builder/flutter-architecture"><img src="https://agentmods.dev/badge/skills/yendangn/flutter-app-builder/flutter-architecture.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.00064 | $0.01329 |
| Opus 5 | $0.00032 | $0.00665 |
| Sonnet 5 | $0.00013 | $0.00266 |
| Haiku 4.5 | $0.00006 | $0.00133 |
Grade A, and why
flutter-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 4d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Architecture
Full reference: template.md
Feature folder structure
lib/src/features/<feature>/
domain/
entities/ ← pure Dart, Equatable, immutable
repositories/ ← abstract interface (contract)
usecases/ ← one class per use case, extends UseCase<T, Params>
data/
dtos/ ← @JsonSerializable, toEntity(), fromJson()
data_sources/ ← interface + impl (remote wraps ApiClient, local wraps DAO)
repositories/ ← implements domain interface, uses BaseRepository mixin
presentation/
cubit/ ← extends BaseCubit, depends on use cases only
pages/ ← BasePage, BlocProvider at page level
widgets/ ← feature-private widgets
di/
<feature>_module.dart ← registers this feature's deps into getIt
Key rules
- Domain layer has zero Flutter/third-party imports. Only pure Dart +
equatable. - Cubits never import repositories — only use cases.
- Data sources are the only layer that knows about network/DB. Remote data source imports
ApiClient. Local imports DAO. - Repository impl uses
BaseRepository.safeCallto wrap errors. Maps DTOs → entities. - Use cases are thin — one
call()method, delegates to repository. No business logic in the use case itself. - Features must not import other features'
domain/ordata/layers. Cross-feature communication goes throughcore/.
Layer dependency direction
presentation → domain ← data
presentation: cubit → use case → repository interface
data: repository impl → data source → ApiClient/DAO
SOLID in Flutter clean architecture
| Principle | How it maps |
|---|---|
| S — Single Responsibility | One use case per class. One cubit per feature screen. Data source only talks to network/DB; repository only maps and guards errors. |
| O — Open/Closed | Add behaviour by adding new use cases or repository methods, never by modifying existing ones. Extend BaseRepository, BaseCubit — don't patch them. |
| L — Liskov Substitution | RepositoryImpl must be a drop-in for its interface. MockRepository in tests must honour the same contract. Any impl that changes observable behaviour (throws when interface says it won't) is a violation. |
| I — Interface Segregation | Repository interfaces expose only what the feature needs — split TaskReadRepository / TaskWriteRepository rather than one fat interface when cubits only read or only write. Data sources have separate RemoteDataSource and LocalDataSource interfaces. |
| D — Dependency Inversion | Cubits depend on UseCase, not RepositoryImpl. Use cases depend on repository interfaces, not impls. DI module wires the concrete impl — nothing else knows about it. |
What ships with it
9 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.
- references/data_layer.md 4.8 KB
- references/di_and_routing.md 2.2 KB
- references/domain_layer.md 3.0 KB
- references/layer_overview.md 3.7 KB
- references/presentation_layer.md 12 KB
- references/rules_and_antipatterns.md 7.1 KB
- references/template.md 4.4 KB
- references/tests.md 5.0 KB
- references/when_to_use.md 1.8 KB
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.
- 4d ago First seen · 100 lines · 64 tokens per session scan A 2e673be1b43f
flutter-architecture is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 1,329 once invoked, about $0.0003 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.