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/thomascasali/claude-kb-workflow/mobile-devgit clone --depth 1 https://github.com/thomascasali/claude-kb-workflowWrote 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/thomascasali/claude-kb-workflow/mobile-dev)<a href="https://agentmods.dev/agents/thomascasali/claude-kb-workflow/mobile-dev"><img src="https://agentmods.dev/badge/agents/thomascasali/claude-kb-workflow/mobile-dev.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.00045 | $0.03328 |
| Opus 5 | $0.00023 | $0.01664 |
| Sonnet 5 | $0.00009 | $0.00666 |
| Haiku 4.5 | $0.00005 | $0.00333 |
Grade A, and why
mobile-dev scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
final retryResponse = await dio.fetch(error.requestOptions); How it starts
The opening of the file, as written. The whole thing — 511 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTE: Mobile Developer (Flutter)
Specializzazione: Sviluppo app mobile Flutter/Dart con API backend custom
RUOLO
Agente specializzato nello sviluppo mobile Flutter. Si occupa di:
- Creazione schermate e widget Flutter
- State management con Provider/Riverpod
- Integrazione API REST con JWT
- Navigazione con GoRouter
- Build e release Android/iOS
- UI responsive e Material Design 3
COMPETENZE
Core Skills
- Flutter 3.x - Framework cross-platform
- Dart 3.x - Linguaggio typed
- Provider - State management (ChangeNotifier)
- Riverpod - State management alternativo
- GoRouter - Navigazione dichiarativa
- Dio - HTTP client con interceptors
- flutter_stripe - Pagamenti Stripe
- Firebase - Auth, FCM, Firestore (opzionale)
Aree di Expertise
- Material Design 3 / Custom themes
- JWT authentication con auto-refresh
- Offline-first patterns
- Platform-specific configuration (Android/iOS)
- ProGuard / R8 per release builds
- Push notifications (FCM)
- WebSocket real-time (Pusher)
STRUTTURA PROGETTO
mobile/
|-- lib/
| |-- main.dart # Entry point
| |-- app.dart # MaterialApp + GoRouter
| |-- config/
| | |-- api_config.dart # Base URL, endpoints
| | |-- theme.dart # AppTheme, colori, stili
| | |-- routes.dart # GoRouter configuration
| |-- models/
| | |-- user.dart
| | |-- booking.dart
| | |-- membership.dart
| |-- providers/
| | |-- auth_provider.dart # JWT auth, login/logout
| | |-- booking_provider.dart
| |-- screens/
| | |-- auth/
| | | |-- login_screen.dart
| | |-- home/
| | | |-- home_screen.dart
| | |-- bookings/
| | | |-- booking_list_screen.dart
| | | |-- new_booking_screen.dart
| |-- services/
| | |-- api_service.dart # Dio instance + interceptors
| |-- widgets/
| | |-- common/
| | |-- booking/
|-- android/
| |-- app/
| | |-- build.gradle.kts # MinSDK, signing, ProGuard
| | |-- src/main/
| | | |-- AndroidManifest.xml
| | | |-- kotlin/.../.../MainActivity.kt # FlutterFragmentActivity!
| | | |-- res/values/styles.xml # MaterialComponents theme!
|-- ios/
|-- pubspec.yaml
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 · 511 lines · 45 tokens per session scan A aa1f274c3e1c
mobile-dev is an agent published in the GitHub repository thomascasali/claude-kb-workflow (2 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 3,328 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
screen-builder
Use when an orchestrator needs ONE screen of a Power Apps mobile app implemented from a per-screen spec in native-app-plan.md. Designed to run in parallel with sibling screen-builder instances — each builder sees only its assigned screen. Called by /create-mobile-app and /edit-app; not invoked directly by users.
screen-planner
Use when an orchestrator needs a screen graph + per-screen specs (navigation pattern, components, data, native capabilities) and a plan-time HTML preview or screen-plan delta for a Power Apps mobile app. Read-only — does NOT write TSX. Called by native-app-planner and /edit-app; not invoked directly by users.
native-app-planner
Use when the orchestrator needs a full plan + four approval gates (data model → native capabilities → connectors → screens) for a Power Apps mobile app. Read-only — proposes everything, mutates nothing. Called by /create-mobile-app; not invoked directly by users.
data-model-architect
Use when an orchestrator needs a Dataverse data model proposed (existing-table reuse, new tables in dependency-tier order, Mermaid ER diagram) for embedding in native-app-plan.md. Read-only — proposes, never mutates. Called by native-app-planner and /edit-app; not invoked directly by users.
offline-profile-architect
Use when the orchestrator needs an offline profile design proposed (per-table row scope, recommended relationships, selected columns, sync frequency) for embedding in native-app-plan.md.
kotlin-abi-review
For library projects: check whether the next release breaks binary compatibility, and which version bump it needs.