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/sampaio-tech/flutter-core-modules/riverpod-patternsgit clone --depth 1 https://github.com/sampaio-tech/flutter-core-modulesWhat 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.01410 |
| Opus 5 | $0.00000 | $0.00705 |
| Sonnet 5 | $0.00000 | $0.00282 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
riverpod-patterns 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 yesterday.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Riverpod + Hooks Rules — flutter_core_modules
Package Imports
The project uses hooks_riverpod v3.x. StateNotifier APIs require the legacy import:
// For StateNotifier, StateNotifierProvider:
import 'package:hooks_riverpod/legacy.dart';
// For Provider, HookConsumerWidget, WidgetRef, etc.:
import 'package:hooks_riverpod/hooks_riverpod.dart';
// For hooks (useState, useEffect, useMemoized, etc.):
import 'package:flutter_hooks/flutter_hooks.dart';
Never use StateNotifier with the main hooks_riverpod.dart import — it is not exported in v3.x and will cause a compile error.
Widget Base Classes
| Need | Base Class |
|---|---|
| Riverpod + hooks | HookConsumerWidget |
| Hooks only | HookWidget |
| Riverpod only | ConsumerWidget |
| Neither | StatelessWidget |
// CORRECT
class MyWidget extends HookConsumerWidget {
@override
Widget build(BuildContext context, WidgetRef ref) { ... }
}
// WRONG — StatelessWidget with hooks causes runtime error
class MyWidget extends StatelessWidget {
Widget build(BuildContext context) {
final state = useState(false); // CRASH
}
}
Provider Types
| Use Case | Type |
|---|---|
| Sync singleton (no dispose) | Provider<T> |
| Sync, auto-dispose | Provider.autoDispose<T> |
| Parameterized | Provider.family<T, Arg> |
| Mutable state, global | StateNotifierProvider<N, S> |
| Mutable state, scoped | StateNotifierProvider.autoDispose<N, S> |
| Mutable state, parameterized | StateNotifierProvider.autoDispose.family<N, S, Arg> |
autoDispose Rules
Always use autoDispose: use cases, repository implementations, screen-scoped notifiers.
Never use autoDispose: global app-lifecycle providers — sharedPreferencesProvider, themeStateNotifierProvider, customerInfoStateNotifierProvider, hapticFeedbackStateNotifierProvider, wakelockStateNotifierProvider, inAppReviewStateNotifierProvider, launchFeedbackStateNotifierProvider.
ref.watch vs ref.read
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.
- yesterday First seen · 203 lines · 0 tokens per session scan A 622195171cc2
riverpod-patterns is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,410 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.