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/arenukvern/mcp_flutter/flutter-mcp-toolkit-debugnpx skills add Arenukvern/mcp_flutter --skill flutter-mcp-toolkit-debuggit 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/skills/arenukvern/mcp_flutter/flutter-mcp-toolkit-debug)<a href="https://agentmods.dev/skills/arenukvern/mcp_flutter/flutter-mcp-toolkit-debug"><img src="https://agentmods.dev/badge/skills/arenukvern/mcp_flutter/flutter-mcp-toolkit-debug.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.1 | $0.00032 | $0.04124 |
| Opus 5 | $0.00016 | $0.02062 |
| Sonnet 5 | $0.00006 | $0.00825 |
| Haiku 4.5 | $0.00003 | $0.00412 |
Grade A, and why
flutter-mcp-toolkit-debug 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 — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill when something broke and you need to understand why:
- A tool call returned an error envelope (
ok: false). - The app behaves unexpectedly and you need runtime log output.
- You need to inspect live app state without changing it (read
AgentState.instance.value). - A prior
controlaction (tap, hot_reload, navigate) completed without error but the result is wrong.
Do NOT use this skill for:
- Reading what is currently on screen — use
flutter-mcp-toolkit-inspect. - The toolkit itself failing to connect — load
flutter-mcp-toolkit-setup.
Registry vs bundled tools
- Bundled
fmt_*tools (screenshot, logs, evaluate, …) run on the MCP server viaAgentRegistryon the host. - App-registered surfaces appear after
MCPToolkitBinding.addEntries/AgentCallEntry— discover withfmt_list_client_tools_and_resources, thenfmt_client_tool/fmt_client_resource.
Triage flow
- Error envelope returned? Read
error.codefirst, thenerror.descriptor.retryable. Look the code up in the Error envelope playbook below. - Retryable error? Run
flutter-mcp-toolkit doctor --json. If doctor fails, loadflutter-mcp-toolkit-setup. - Need log output? Call
get_recent_logswithcount: 100and a level filter. Look for stack traces or assertion messages near the timestamp of the failure. - Need live state? Call
evaluate_dart_expressionwith a targeted expression (e.g.MyBloc.instance.state.toString()). Do this after logs, not instead of them. - Chaining with inspect? Order:
semantic_snapshot→evaluate_dart_expression→get_recent_logs. Snapshot gives you the current widget tree before expression evaluation mutates nothing; logs give trailing context. - Multiple targets? If
connection_selection_required, calldiscover_debug_apps, pick thetargetId, then passconnection: {targetId: "..."}to every subsequent call.
Tool reference
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 · 389 lines · 32 tokens per session scan A 16e908c7b952
flutter-mcp-toolkit-debug is a skill published in the GitHub repository Arenukvern/mcp_flutter (373 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 4,124 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-database
Use when syncing real-time data, structuring JSON trees, reading/writing, creating listeners, enabling offline persistence, managing presence, sharding, or writing security rules.
flutter-app-architecture
Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).