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.
git clone --depth 1 https://github.com/smicolon/ai-kitWrote 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/commands/smicolon/ai-kit/flutter-test)<a href="https://agentmods.dev/commands/smicolon/ai-kit/flutter-test"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/flutter-test/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/commands/smicolon/ai-kit/flutter-test"><img src="https://agentmods.dev/badge/commands/smicolon/ai-kit/flutter-test.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.00591 |
| Opus 5.5 | $0.00006 | $0.00236 |
| Sonnet 5.5 | $0.00003 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
flutter-test 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Test Command
Run Flutter tests with optional coverage reporting.
Parse Arguments
Extract from user input:
- type:
unit,widget,integration, orall(default: all) - coverage: Include
--coverageflag - update-goldens: Include
--update-goldensfor golden tests - filter: Optional test file pattern
Test Discovery
Locate tests based on type:
- unit:
test/unit/**/*_test.dartortest/**/*_test.dart(excluding integration) - widget:
test/widget/**/*_test.dartor tests withtestWidgets - integration:
integration_test/**/*_test.dart
Test Commands
Run All Tests
flutter test
Run with Coverage
flutter test --coverage
Run Specific Test File
flutter test test/unit/auth_test.dart
Run Integration Tests
flutter test integration_test/app_test.dart
Update Golden Files
flutter test --update-goldens
Coverage Report
When --coverage is requested:
- Run tests with coverage:
flutter test --coverage
- Generate HTML report (if lcov installed):
genhtml coverage/lcov.info -o coverage/html
- Report coverage summary:
lcov --summary coverage/lcov.info
Execution Steps
- Display test configuration
- Run
flutter pub getif needed - Execute test command(s)
- Parse and display results:
- Total tests run
- Passed/Failed/Skipped counts
- Failed test details
- Coverage percentage (if enabled)
Coverage Analysis
If coverage enabled, analyze:
- Overall line coverage percentage
- Files with low coverage (<80%)
- Uncovered critical paths
Error Handling
If tests fail:
- Show failed test names and locations
- Display assertion messages
- Suggest fixes if patterns detected
Output Format
Flutter Tests Summary
=====================
Total: 150
Passed: 145
Failed: 3
Skipped: 2
Failed Tests:
- test/unit/auth_service_test.dart: 'should handle invalid credentials'
- test/widget/login_form_test.dart: 'shows error on empty email'
Coverage: 87.3% (target: 80%)
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.
- 1mo ago First seen · 118 lines · 16 tokens per session scan A 53a424321aaa
flutter-test is a command published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 591 once invoked, about $0.0001 per session on Opus 5.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-31.
Other commands, from other repositories
xcode-test
Build and test iOS apps on simulator using XcodeBuildMCP.
axiom-ui
Drive simulator UI with an external xcui or AXe installation when available.
generate-widget
Génération Widget Flutter avec Tests.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.
test-bar
Generate a floating QA test overlay for the current branch's UI changes. Use when user says /test-bar, needs visual QA scenarios, or wants to test conditional rendering paths.
write-skill-test
RED-GREEN-REFACTOR implementation for writing-skills: Baseline testing, minimal skill writing, loophole closure, and full creation checklist.