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/paulpham157/paul-s-cursor-rules/flutter-performance-rulesgit clone --depth 1 https://github.com/paulpham157/paul-s-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/paulpham157/paul-s-cursor-rules/flutter-performance-rules)<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/flutter-performance-rules"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/flutter-performance-rules.svg" alt="Measured on agentmods" 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.00078 |
| Opus 5 | $0.00000 | $0.00039 |
| Sonnet 5 | $0.00000 | $0.00016 |
| Haiku 4.5 | $0.00000 | $0.00008 |
Grade A, and why
flutter-performance-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.
Copies of this mod
2 near-identical copies found in the catalogue:
- flutter-performance-rules — 100% identical, 0 lines differ
- flutter-performance-rules — 100% identical, 0 lines differ
What it actually says
- Use proper image caching.
- Implement proper list view optimization.
- Use proper build methods optimization.
- Follow proper state management patterns.
- Implement proper memory management.
- Use proper platform channels when needed.
- Follow proper compilation optimization techniques.
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 · 11 lines · 0 tokens per session scan A dafebbdc5da4
flutter-performance-rules is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 78 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-09-03.
Other cursor rules, from other repositories
swift-uikit-cursorrules-prompt-file
Cursor rules for Swift Uikit.
flutter-riverpod-cursorrules-prompt-file
Cursor rules for Flutter Riverpod.
swiftui-guidelines-cursorrules-prompt-file
Cursor rules for SwiftUI development guidelines.
flutter-app-expert-cursorrules-prompt-file
Cursor rules for Flutter development with expert integration.
nativescript
NativeScript best practices and patterns for mobile applications.
android-jetpack-compose-cursorrules-prompt-file
Cursor rules for Android development with Jetpack Compose integration.