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 skills/sampaio-tech/flutter-core-modules/riverpod-hooks-patternsnpx skills add sampaio-tech/flutter-core-modules --skill riverpod-hooks-patternsgit clone --depth 1 https://github.com/sampaio-tech/flutter-core-modulesWrote 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/skills/sampaio-tech/flutter-core-modules/riverpod-hooks-patterns)<a href="https://agentmods.dev/skills/sampaio-tech/flutter-core-modules/riverpod-hooks-patterns"><img src="https://agentmods.dev/badge/skills/sampaio-tech/flutter-core-modules/riverpod-hooks-patterns.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 | $0.00064 | $0.02905 |
| Opus 5 | $0.00032 | $0.01452 |
| Sonnet 5 | $0.00013 | $0.00581 |
| Haiku 4.5 | $0.00006 | $0.00291 |
Grade A, and why
riverpod-hooks-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 4d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Riverpod + flutter_hooks Patterns — flutter_core_modules
This package uses hooks_riverpod (v3.x) + flutter_hooks (v0.21.x). Every widget that needs either Riverpod or hooks extends HookConsumerWidget. Every widget that needs only hooks extends HookWidget.
1. Provider Type Selection Guide
| Use Case | Provider Type | Example in Codebase |
|---|---|---|
| Sync read-only value | Provider |
sharedPreferencesProvider, amplitudeProvider |
| Sync read-only, dispose when unused | Provider.autoDispose |
cacheRepositoryProvider, getBoolUsecaseProvider |
| Parameterized provider | Provider.family |
navigatiorKeyProvider |
| Mutable state, no async | StateNotifierProvider |
themeStateNotifierProvider, hapticFeedbackStateNotifierProvider |
| Mutable state, dispose when unused | StateNotifierProvider.autoDispose |
— |
| Mutable state + params | StateNotifierProvider.autoDispose.family |
getDownloadUrlStateNotifierProvider, getJsonStateNotifierProvider |
| Derived/computed value | Provider watching another |
isPremiumCustomerProvider |
2. When to Use autoDispose
Use autoDispose for:
- Use cases (they have no state, just method calls)
- Repository implementations (stateless)
- Feature-specific state that only lives while a screen is visible
Do NOT use autoDispose for:
- Global app state:
themeStateNotifierProvider,hapticFeedbackStateNotifierProvider,wakelockStateNotifierProvider - RevenueCat:
customerInfoStateNotifierProvider(persists subscription state) - In-app review:
inAppReviewStateNotifierProvider,launchFeedbackStateNotifierProvider - Riverpod root providers:
sharedPreferencesProvider(singleton)
3. State Flow Through Layers
UI (HookConsumerWidget)
│
├── ref.watch(myStateNotifierProvider) ← subscribe to State<F, S>
├── ref.read(myStateNotifierProvider.notifier) ← call methods
└── ref.read(myUsecaseProvider) ← direct use case access
│
└── StateNotifier (SafeStateNotifier subclass)
│
└── UseCase.call(...)
│
└── Repository.method(...) ← Either<Failure, T>
│
└── DataSource / SDK
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.
- 4d ago First seen · 405 lines · 64 tokens per session scan A 386cc80b5810
riverpod-hooks-patterns is a skill published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 13d ago), licensed MIT. It adds 64 tokens to every session and 2,905 once invoked, about $0.0003 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…