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/MoritzMessner/flutter-cursor-rulesWrote 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/rules/moritzmessner/flutter-cursor-rules/flutter_testing)<a href="https://agentmods.dev/rules/moritzmessner/flutter-cursor-rules/flutter_testing"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/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/rules/moritzmessner/flutter-cursor-rules/flutter_testing"><img src="https://agentmods.dev/badge/rules/moritzmessner/flutter-cursor-rules/flutter_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.00000 | $0.00493 |
| Opus 5.5 | $0.00000 | $0.00197 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
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 2mo 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🧪 Testing Strategy
Unit Test: ViewModels
Test that the ViewModel correctly updates its state (and Commands) in response to actions.
void main() {
group('HomeViewModel', () {
late HomeViewModel viewModel;
late MockBookingRepository mockRepo;
setUp(() {
mockRepo = MockBookingRepository();
viewModel = HomeViewModel(bookingRepository: mockRepo, ...);
});
test('loads bookings successfully', () async {
when(mockRepo.getBookings()).thenAnswer((_) async => Result.ok(bookings));
await viewModel.loadData.execute();
expect(viewModel.items, bookings);
expect(viewModel.loadData.completed, true);
});
test('handles error', () async {
when(mockRepo.getBookings()).thenAnswer((_) async => Result.error(Exception()));
await viewModel.loadData.execute();
expect(viewModel.loadData.error, true);
});
});
}
Unit Test: Repositories
Test that the Repository correctly coordinates between Services (API, Cache) and handles errors.
void main() {
group('BookingRepository', () {
// ... setup mocks
test('returns cached data when available', () async {
when(mockCache.getBookings()).thenAnswer((_) async => cachedBookings);
final result = await repository.getBookings();
expect((result as Ok).value, cachedBookings);
verifyNever(mockApi.get(any));
});
test('fetches from API when cache is empty', () async {
when(mockCache.getBookings()).thenAnswer((_) async => null);
when(mockApi.get('/bookings')).thenAnswer((_) async => apiResponse);
final result = await repository.getBookings();
expect(result, isA<Ok<List<Booking>>>());
verify(mockApi.get('/bookings')).called(1);
});
});
}
Widget Tests
Test UI rendering in different states (Loading, Error, Data).
testWidgets('shows loading indicator', (tester) async {
when(mockViewModel.loadData).thenReturn(MockCommand()..running = true);
await tester.pumpWidget(MaterialApp(home: HomeScreen(viewModel: mockViewModel)));
expect(find.byType(CircularProgressIndicator), findsOneWidget);
});
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.
- 2mo ago First seen · 75 lines · 0 tokens per session scan A 2d726a26946a
flutter_testing is a cursor rule published in the GitHub repository MoritzMessner/flutter-cursor-rules (4 stars, last pushed 21d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 493 tokens. 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 cursor rules, from other repositories
mobile-testing-patterns
Testing structure and colocated test conventions.
xcodebuildmcp-tools
Comprehensive guide for using XcodeBuildMCP tools for building, testing, deploying, and automating iOS applications. Includes simulator management, device deployment, UI automation, and debugging workflows. Apply when building apps, running tests, automating workflows, or using development tools.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.
flutter-testing-rules
Specifies testing guidelines for Flutter projects, covering unit, widget, and integration tests.
android-jetpack-compose---testing-guidelines
Defines testing guidelines for Android Jetpack Compose components, ViewModels, and UseCases.
122-swift-development
122: Swift development workflow including TDD, refactoring, and performance optimization.