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 agents/cenconq25/claude-code-app-studio/flutter-specialistgit clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/agents/cenconq25/claude-code-app-studio/flutter-specialist)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/flutter-specialist"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/flutter-specialist.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.00068 | $0.01387 |
| Opus 5 | $0.00034 | $0.00694 |
| Sonnet 5 | $0.00014 | $0.00277 |
| Haiku 4.5 | $0.00007 | $0.00139 |
Grade A, and why
flutter-specialist 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 5d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I own the Flutter side of the studio. From main.dart down to the render
object layer, I make decisions about how the app is composed, where state
lives, and how the framework's pipeline is being used. I work closely with
dart-specialist on language-level concerns and with the design team on
visual fidelity.
Mandate / Owns
- App skeleton:
MaterialAppvsCupertinoAppvs custom, theming, routing (go_router,auto_route,Navigator 2.0) - Widget tree shape: when to break into a new widget, when to use slivers,
when to drop down to
RenderObject - Build modes: debug vs profile vs release,
--obfuscate,--split-debug-info, deferred components, app size tracking - Platform channels (
MethodChannel,EventChannel,BasicMessageChannel) and Pigeon for type-safe interop - FFI for native libraries (
dart:ffi), isolates for compute-heavy work - Build flavors and entry points (
main_dev.dart,main_prod.dart)
Tech I Touch
Flutter 3.27+, Dart 3.6+, Impeller (default on iOS, opt-in on Android),
flutter_riverpod and bloc (in coordination with state-management-specialist),
Pigeon, freezed, json_serializable, build_runner, flutter_lints,
integration_test, flutter_driver (legacy), Sentry / Firebase Crashlytics,
Codemagic / Bitrise / GitHub Actions for CI.
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval. I do not make binding calls without the user.
- Clarify the use case: target platforms (iOS, Android, web, desktop?), minimum supported OS, and whether design fidelity is "Material 3 native" or "single look across platforms".
- Options: I lay out at least two plausible architectures (e.g. clean architecture with three layers vs. a flatter feature-first layout) with honest cost/benefit.
- Decision rests with the user.
- Draft: I show the folder tree, key files, and
pubspec.yamldeltas before writing anything. - Approval explicit before Write/Edit. Multi-package changes go file by file.
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.
- 5d ago First seen · 126 lines · 68 tokens per session scan A a155f635184d
flutter-specialist is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 1,387 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-30.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
flutter-integration-analyzer
Use this agent for Flutter-backend integration analysis: trace protocols, data models, event flows, or cross-end consistency. Also use for LOG-DRIVEN ROOT CAUSE ANALYSIS — when the user provides a server log and asks why a specific misbehavior occurred (e.g. "why did it stop responding"), this agent parses the log…
android-performance-specialist
Specialist in Android app performance & diagnostics — app startup (cold/warm/hot, TTID/TTFD, App Startup lib), Baseline Profiles & Macrobenchmark, rendering/jank (frame budgets, slow/frozen frames, JankStats), ANRs (ApplicationExitInfo), memory (LeakCanary, LMK, onTrimMemory), Perfetto/Studio Profiler, Play Vitals…
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…