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 skills add MADTeacher/mad-agents-skills --skill flutter-testinggit clone --depth 1 https://github.com/MADTeacher/mad-agents-skillsWrote 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/madteacher/mad-agents-skills/flutter-testing)<a href="https://agentmods.dev/skills/madteacher/mad-agents-skills/flutter-testing"><img src="https://agentmods.dev/badge/skills/madteacher/mad-agents-skills/flutter-testing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/madteacher/mad-agents-skills/flutter-testing"><img src="https://agentmods.dev/badge/skills/madteacher/mad-agents-skills/flutter-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00093 | $0.01295 |
| Opus 5 | $0.00046 | $0.00647 |
| Sonnet 5 | $0.00019 | $0.00259 |
| Haiku 4.5 | $0.00009 | $0.00129 |
Grade A, and why
flutter-testing 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 9d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Testing
You are a Flutter testing engineer for app, package, and plugin projects.
Principle 0
Do not write Flutter tests from memory. First inspect the project, choose the right test layer, read the routed reference for the scenario, then run the closest validation command. Broken or flaky tests waste more time than missing tests because they create false confidence and slow future changes.
Workflow
- Inspect the project before changing tests:
pubspec.yaml, existingtest/,integration_test/,test_driver/, generated mock files, state management, platform abstractions, plugin usage, and CI commands. - Choose the test layer:
- Pure Dart functions, repositories, services, state reducers, and view models: unit tests.
- Single widgets, forms, navigation shells, semantics, gestures, responsive layout, and UI state: widget tests.
- Complete user flows, real device behavior, screenshots, performance reports, native/plugin bridges, and browser/device targets: integration tests.
- Flutter plugins or app code using platform channels: plugin and mocking guidance.
- Read only the reference files needed for the chosen scenario.
- Implement the smallest deterministic test or test fix using the project's existing test style, dependency injection pattern, keys, fixtures, mocks, and CI constraints.
- Run mandatory validation. If validation cannot run, report the exact blocker and the concrete risk instead of presenting the change as verified.
Resource Routing
| Task | Read or run | Why |
|---|---|---|
| Write or fix pure Dart tests, async tests, stream tests, matchers, exceptions, or test organization | references/unit-testing.md |
Unit-test patterns that compile under Dart null safety |
| Write or fix widget tests, finders, gestures, forms, navigation, semantics, scrolling, animations, or layout-size tests | references/widget-testing.md |
flutter_test APIs and widget-specific pitfalls |
| Add or fix integration tests, device/browser runs, performance reports, screenshots, persistence flows, platform scenarios, or CI integration | references/integration-testing.md |
Current integration_test APIs and target commands |
| Mock dependencies, repositories, platform channels, generated Mockito mocks, manual fakes, or state-management collaborators | references/mocking.md |
Deterministic test-double patterns and mock generation |
Diagnose failing tests, layout errors, MissingPluginException, finder failures, timeouts, async hangs, or debugging output |
references/common-errors.md |
Error-to-fix mapping without guessing |
| Test Flutter plugin packages, native Android/iOS code, example-app integration tests, or plugin registration/error paths | references/plugin-testing.md |
Plugin package layout and native/Dart test split |
| Edit this skill, references, or examples | scripts/verify-examples.sh |
Deterministic smoke check for stale patterns and broken links |
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 107 lines · 93 tokens per session scan A a3ce731b8d2e
flutter-testing is a skill published in the GitHub repository MADTeacher/mad-agents-skills (108 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 1,295 once invoked, about $0.0005 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 skills, from other repositories
flutter-testing
Covers Flutter testing across all three layers: unit tests (business logic, ViewModels, repositories), widget tests (UI rendering, interactions, golden regression), and integration/E2E tests (full app flows, native OS interactions). Use this skill when writing any Flutter test, setting up mocking with mocktail or…
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
flutter-mcp-toolkit-control
Drive a running Flutter app — tap, scroll, type, fill forms, hot-reload, navigate. Use when you need to interact with the UI.
flutter-mcp-cli-runtime-validation
Run Flutter MCP runtime validation from CLI in two steps (launch app, then run validate-runtime), including toolkit-extension gating, screenshot/layout capture, app error collection, optional reload verification, and retry handling for transient first-connect failures.
fluttersdk-dusk
End-to-end driver for Flutter apps, designed for LLM agents. The running app exposes a ext.dusk. VM Service surface plus an MCP server; the agent calls dusk tools (or ./bin/fsa dusk: from a shell) to snap the Semantics tree, mint ref tokens, gesture against them, wait for conditions, screenshot, and hot-reload, all…
testing-with-marionette
AI-driven Flutter E2E testing via VM Service CLI. Control running Flutter apps in debug mode for smoke tests, regression checks, exploratory testing, and UI automation. Trigger when user mentions E2E testing, UI automation, smoke tests, integration testing, test automation, controlling Flutter apps, VM Service…