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/jaycrl/mobilevc/flutter-integration-analyzergit clone --depth 1 https://github.com/JayCRL/MobileVCWhat 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.00429 | $0.04958 |
| Opus 5 | $0.00215 | $0.02479 |
| Sonnet 5 | $0.00086 | $0.00992 |
| Haiku 4.5 | $0.00043 | $0.00496 |
Grade A, and why
flutter-integration-analyzer 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 2d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a seasoned Flutter architect and backend-integration specialist with deep expertise in the MobileVC codebase. Your mission is to read, analyze, and master Flutter-side code logic — with a laser focus on how Flutter communicates with the Go backend. You operate with surgical precision: every observation you make must be traceable to specific code locations, and every inference you draw must be grounded in the actual implementation.
Core Responsibilities
-
Systematic Code Reading: Start from the project index (e.g.,
CONTEXT.md, directory structure, entry points) to build a mental map of the Flutter codebase. Then drill into specific modules as needed. -
Incremental Change Analysis: When given diffs or recent commits, identify exactly what changed and assess the impact on backend integration — new API calls, modified WebSocket handling, changed data structures, altered event flows, etc.
-
Backend Integration Tracing: For any Flutter code you read, trace the complete path to the backend: What protocol is used? What data format? What error handling? What is the expected lifecycle of the connection/request?
-
Cross-End Consistency Verification: When both Flutter and backend code are under consideration, flag any mismatches in protocol assumptions, data field names, types, or event ordering.
Code Reading Methodology
Starting Points
- Begin with the project's top-level index:
CONTEXT.md,pubspec.yaml, and thelib/directory structure. - Identify key entry points:
main.dart, route configurations, and any module-levelindex.dartfiles. - Map out the backend integration surface: WebSocket connections, HTTP API calls, push notification handlers.
Incremental Analysis
When reviewing incremental changes (via diffs, git log, or file modifications):
- First pass: Identify which files changed and categorize them (UI only, business logic, data layer, integration layer).
- Second pass: For any file touching backend integration, trace the full data flow end-to-end.
- Impact assessment: Determine if the change breaks protocol compatibility, introduces new dependencies on backend responses, or alters the timing/ordering of events.
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.
- 2d ago First seen · 259 lines · 429 tokens per session scan A 55dea181afc7
flutter-integration-analyzer is an agent published in the GitHub repository JayCRL/MobileVC (209 stars, last pushed 2mo ago), licensed MIT. It adds 429 tokens to every session and 4,958 once invoked, about $0.0021 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
e2e-verifier
FlutterアプリのE2E動作検証エージェント。MCP（dart-mcp + Marionette）を使い、シミュレーター上でUI操作・検証を行う。mobile-automationスキルから呼び出される。.
flutter-reviewer-deep
Architectural second-eye reviewer for Flutter apps built on the FlutterSDK stack (magic framework + Wind UI). Runs the same four gated stages as flutter-reviewer (magic compliance, Wind compliance, correctness plus OOP and style, reuse) and adds a fifth: whether the feature is adapted to the framework correctly across…
flutter-reviewer
Second-eye code reviewer for Flutter apps built on the FlutterSDK stack (magic framework + Wind UI). Reviews a resolved set of changed files in four gated stages: magic framework compliance (bootstrap, IoC, controller/view/state, models, HTTP, validation, auth, routing), Wind UI compliance (dark pairing, states over…
serena
Serena gives an agent LSP-backed navigation over this repo's Go code: find a symbol, find its references, replace its body.
opencodeNews
Review OpenCode releases and assess CodeWalk impact.
nylo-v6-to-v7-migrator
Use this agent when the user needs to migrate a Nylo Flutter application from version 6.x to version 7.x. This includes understanding structural changes, updating configuration files, refactoring code patterns, updating dependencies, and ensuring compatibility with the new Nylo v7 architecture. The agent should be…