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 rules/ricardocaste/flutter-cursor-rules/flutter-testing-rulesgit clone --depth 1 https://github.com/ricardocaste/flutter-cursor-rulesWhat 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 | $0.00000 | $0.00077 |
| Opus 5 | $0.00000 | $0.00039 |
| Sonnet 5 | $0.00000 | $0.00015 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
flutter-testing-rules 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.
What it actually says
- Write unit tests for business logic.
- Implement widget tests for UI components.
- Use integration tests for feature testing.
- Implement proper mocking strategies.
- Use proper test coverage tools.
- Follow proper test naming conventions.
- Implement proper CI/CD testing.
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 · 12 lines · 0 tokens per session scan A 96d28b89c85e
flutter-testing-rules is a cursor rule published in the GitHub repository ricardocaste/flutter-cursor-rules (3 stars, last pushed 1y ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 77 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
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.