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/patrickjs/awesome-cursorrules/flutter-riverpod-cursorrules-prompt-filegit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWhat 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.01753 | $0.01753 |
| Opus 5 | $0.00877 | $0.00877 |
| Sonnet 5 | $0.00351 | $0.00351 |
| Haiku 4.5 | $0.00175 | $0.00175 |
Grade A, and why
flutter-riverpod-cursorrules-prompt-file 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 3d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Assistant Technical Instructions
You are an AI assistant with advanced problem-solving capabilities. Please follow these instructions to execute tasks efficiently and accurately.
First, confirm the instructions received from the user:
Please proceed with the following process based on these instructions:
1. Instruction Analysis and Planning
Preventing Duplicate Implementation
Before implementation, verify:
- Existence of similar functionality
- Functions or components with identical or similar names
- Duplicate API endpoints
- Identification of processes that can be shared
Take sufficient time for this section as it guides the entire subsequent process. Conduct thorough and comprehensive analysis. </Task Analysis>
2. Task Execution
- Execute identified steps one by one
- Report progress concisely after completing each step
- Pay attention to the following during implementation:
- Adherence to proper directory structure
- Consistency in naming conventions
- Appropriate placement of shared processes
3. Quality Control and Problem Resolution
-
Quickly verify the execution results of each task
-
If errors or inconsistencies occur, address them through the following process: a. Problem isolation and cause identification (log analysis, debug information verification) b. Creation and implementation of countermeasures c. Post-fix operation verification d. Debug log confirmation and analysis
-
Record verification results in the following format: a. Verification items and expected results b. Actual results and discrepancies c. Required countermeasures (if applicable)
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.
- 3d ago First seen · 283 lines · 0 tokens per session scan A c63349937338
flutter-riverpod-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,694 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,753 tokens to every session, about $0.0088 per session on Opus 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-30.
Other cursor rules, from other repositories
react-native
React Native: mobile app development, navigation, native modules.
expo
Expo/React Native: native modules, navigation, platform-specific code.
flutter
Flutter: Riverpod, widget extraction, Dart 3.
swiftui
SwiftUI best practices for iOS, macOS, and cross-platform Apple development.
flutter
Flutter best practices with Dart, state management, and Material 3 design.
react-native
React Native with Expo best practices for mobile app development.