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 launch52-ai/flutter-template --skill testinggit clone --depth 1 https://github.com/launch52-ai/flutter-templateWrote 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/launch52-ai/flutter-template/testing)<a href="https://agentmods.dev/skills/launch52-ai/flutter-template/testing"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/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/launch52-ai/flutter-template/testing"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/testing.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.00050 | $0.00772 |
| Opus 5.5 | $0.00020 | $0.00309 |
| Sonnet 5.5 | $0.00010 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
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 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.
Testing - Write & Review Tests
Write high-quality, maintainable tests following Clean Architecture patterns. Every test should clearly express intent and catch regressions without being brittle.
When to Use This Skill
- Writing new tests (unit, widget, golden, integration)
- Reviewing test code quality
- Setting up test infrastructure (helpers, mocks, spies)
- Testing Riverpod providers and notifiers
- Auditing test coverage
Quick Reference
Test Types
| Type | Purpose | When to Use |
|---|---|---|
| Unit | Isolated logic | Repositories, services, utils, providers |
| Widget | UI interactions | Screens, navigation |
| Golden | Visual regression | Layout, themes |
| Integration | Real implementations | Storage, cache, API flows |
Naming Conventions
| Type | Pattern | Example |
|---|---|---|
| File | {component}_test.dart |
auth_repository_impl_test.dart |
| Test | test_{subject}_{scenario}_{expected} |
test_signIn_withValidCredentials_returnsAuthResult |
| Factory | any{Type}() |
anyEmail(), anyUserProfile() |
| SUT | makeSUT() |
Creates System Under Test |
Commands
# Run all tests
flutter test
# Run with coverage
flutter test --coverage
# Run specific type
flutter test test/unit/
flutter test test/widget/
# Audit test coverage
dart run .claude/skills/testing/scripts/check.dart
# Generate missing test files
dart run .claude/skills/testing/scripts/check.dart --generate
# Update golden files
flutter test --update-goldens test/golden/
Workflow
1. Create Test File
Mirror source path: test/unit/features/{feature}/data/repositories/{name}_test.dart
2. Write Tests Using Patterns
See patterns-guide.md for:
- makeSUT() - Factory for System Under Test
- Spy Pattern - Track method calls
- Arrange-Act-Assert - Clear structure
- Disposal Testing - Verify cleanup
- Inbox Checklist - Infrastructure testing
3. Verify Coverage
What ships with it
14 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.
- examples.md 24 KB
- patterns-guide.md 47 KB
- reference/flutter_test_config.dart 381 B
- reference/golden/features/auth/presentation/screens/login_screen_golden_test.dart 11 KB
- reference/helpers/fakes.dart 12 KB
- reference/helpers/golden_helpers.dart 8.0 KB
- reference/helpers/mocks.dart 4.7 KB
- reference/helpers/pump_app.dart 6.5 KB
- reference/helpers/riverpod_helpers.dart 5.1 KB
- reference/helpers/test_helpers.dart 4.8 KB
- reference/unit/features/auth/data/repositories/auth_repository_impl_test.dart 12 KB
- reference/unit/features/auth/presentation/providers/auth_provider_test.dart 11 KB
- reference/widget/features/auth/presentation/screens/login_screen_test.dart 9.5 KB
- scripts/check.dart 23 KB
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 · 50 tokens per session scan A 18216fef2d49
testing is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 772 once invoked, about $0.0002 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 skills, from other repositories
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions…
flutter-testing
Write, fix, review, debug, and validate Flutter tests for apps, packages, and plugins. Use when adding unit tests, widget tests, integration tests, MethodChannel or plugin mocks, Mockito or mocktail test doubles, golden or accessibility checks, CI test commands, test failures, MissingPluginException, pump or…
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…
nylo-testing
Use when writing, running, or debugging tests in a Nylo v7 Flutter project. Covers widget tests, unit tests, API mocking, factories, authentication simulation, time travel, state testing, and Nylo-specific assertions.