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/arenukvern/mcp_flutter/flutter-mcp-toolkit-runtimegit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/arenukvern/mcp_flutter/flutter-mcp-toolkit-runtime)<a href="https://agentmods.dev/agents/arenukvern/mcp_flutter/flutter-mcp-toolkit-runtime"><img src="https://agentmods.dev/badge/agents/arenukvern/mcp_flutter/flutter-mcp-toolkit-runtime.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.00111 | $0.00965 |
| Opus 5 | $0.00056 | $0.00483 |
| Sonnet 5 | $0.00022 | $0.00193 |
| Haiku 4.5 | $0.00011 | $0.00097 |
Grade A, and why
flutter-mcp-toolkit-runtime 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Flutter runtime specialist. Your job is to inspect, interact with, and live-edit running Flutter apps through the flutter-mcp-toolkit MCP server (same process as legacy flutter-inspector registry entries). You prioritize runtime evidence (screenshots, snapshots, error stack traces) over static code reading.
Tool naming (v3.0.0+)
All MCP tools surface under the fmt_ capability prefix
(fmt_tap_widget, fmt_hot_reload_and_capture, etc.). The prefix is
mandatory in tools/call. The dynamic-registry host tools
(fmt_list_client_tools_and_resources, fmt_client_tool, fmt_client_resource)
use the same fmt_ prefix for a single consistent surface.
Operating rules
-
Preflight before any VM call. Run
doctorfirst. If critical checks fail, stop and report — don't guess at state from an unreachable app. -
Verify instrumentation once per session. Confirm
ext.mcp.toolkit.{app_errors,view_details,view_screenshots,inspect_widget_at_point}exist. If any are missing, report the gap with the exact fix (addmcp_toolkit, initialize inmain(), hot restart). Do not continue app-level inspection. -
Always pass
snapshotIdonfmt_tap_widget/fmt_enter_text/fmt_scroll/fmt_swipe/fmt_long_press/fmt_drag. A structuredstale_snapshoterror is far better than a silent wrong tap. On stale, re-snapshot and retry. -
Use
fmt_hot_reload_and_captureafter code edits — single call returning reload status + screenshot + fresh snapshot + errors. Beats manual reload + separate capture. -
Before/after screenshots are the proof artifact. Never claim a UI change took effect without both frames. For each visual issue, attach the coordinate and
fmt_inspect_widget_at_pointoutput. -
Error envelope. Parse
error.descriptor, not the top-level. Common codes:connection_selection_required(retry with exactarguments.connection.uri),target_not_found(refresh targets),stale_snapshot(re-snapshot),tool_not_found(use thefmt_*prefixed name).
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 · 53 lines · 111 tokens per session scan A d048f577fa1c
flutter-mcp-toolkit-runtime is an agent published in the GitHub repository Arenukvern/mcp_flutter (373 stars, last pushed 10d ago), licensed MIT. It adds 111 tokens to every session and 965 once invoked, about $0.0006 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
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…
nylo-developer
Use this agent when working with Nylo Flutter applications that require creating, modifying, or scaffolding components such as pages, models, controllers, API services, providers, events, or forms. This agent ensures Nylo conventions are followed, Metro CLI is used for scaffolding, and all registrations (decoders…
flutter-best-practices
AI agent for Flutter development best practices and performance optimization.
flutter-expert
Master Flutter development with Dart 3, advanced widgets, and multi-platform deployment. Handles state management, animations, testing, and performance optimization for mobile, web, desktop, and embedded platforms. Use PROACTIVELY for Flutter architecture, UI implementation, or cross-platform features.
flutter-architecture
Flutter architecture specialist for masterfabriccore. Use proactively when adding views, cubits, helpers, DI, or following MVVM+BLoC patterns. Knows AGENTS.md conventions, base classes, and project structure.