awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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.
git clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/riverpod)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/riverpod"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/riverpod.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.03035 | $0.03035 |
| Opus 5 | $0.01517 | $0.01517 |
| Sonnet 5 | $0.00607 | $0.00607 |
| Haiku 4.5 | $0.00303 | $0.00303 |
Grade A, and why
riverpod 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 — 440 lines — stays where its author put it; the contents beside it link to each section on GitHub.
riverpod Best Practices
Riverpod is the definitive state management solution for modern Flutter applications. It provides compile-time safety, unparalleled testability, and a declarative API. This guide outlines our team's mandatory best practices for leveraging Riverpod effectively.
1. Code Organization and Structure
Organize providers by feature or domain, not by provider type. This enhances modularity and discoverability. Always use @riverpod for code generation.
✅ GOOD: Feature-based Provider Grouping
// features/auth/auth_providers.dart
import 'package:riverpod_annotation/riverpod_annotation.dart';
import 'package:your_app/features/auth/auth_service.dart';
part 'auth_providers.g.dart';
@riverpod
AuthService authService(AuthServiceRef ref) {
return AuthServiceImpl(); // Or mock in tests
}
@riverpod
class AuthNotifier extends _$AuthNotifier {
@override
bool build() {
// Initial auth state logic
return false;
}
void login() => state = true;
void logout() => state = false;
}
❌ BAD: Generic or Type-based Grouping
// providers/auth_provider.dart (too generic)
// providers/future_providers.dart (grouped by type, not feature)
final authServiceProvider = Provider<AuthService>((ref) => AuthServiceImpl());
final authNotifierProvider = StateNotifierProvider<AuthNotifier, bool>((ref) => AuthNotifier());
Action: Always run dart run build_runner watch during development to keep .g.dart files up-to-date.
2. Provider Types and Usage
Prefer generated @riverpod classes (Notifier, AsyncNotifier, StreamNotifier) for mutable state and FutureProvider/StreamProvider for immutable async data.
2.1. Mutable State: Notifier and AsyncNotifier
Use Notifier for synchronous mutable state and AsyncNotifier for asynchronous mutable state (e.g., API calls that modify state).
✅ GOOD: AsyncNotifier for state with async operations
// features/todos/todo_providers.dart
import 'package:riverpod_annotation/riverpod_annotation.dart';
import 'package:your_app/features/todos/todo_repository.dart';
import 'package:your_app/features/todos/todo_model.dart';
part 'todo_providers.g.dart';
@riverpod
class TodoListNotifier extends _$TodoListNotifier {
@override
Future<List<Todo>> build() async {
// Initial fetch
return ref.watch(todoRepositoryProvider).fetchTodos();
}
Future<void> addTodo(Todo todo) async {
state = const AsyncValue.loading(); // Show loading state
state = await AsyncValue.guard(() async {
final newTodo = await ref.read(todoRepositoryProvider).addTodo(todo);
return [...state.value!, newTodo]; // Update state immutably
});
}
}
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 · 440 lines · 3,035 tokens per session scan A 48beaf926443
riverpod is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 3,035 tokens to every session, about $0.0152 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-09-03.
Other cursor rules, from other repositories
nativescript
NativeScript best practices and patterns for mobile applications.
performance-optimization
// Use weak/unowned references appropriately class ViewController: UIViewController { private var timer: Timer?
webkit-browser
Cursor rule "webkit-browser" from duckduckgo/apple-browsers, covering webkit & browser development guidelines, webview configuration, basic webview setup, user scripts management and tab management.
maestro-device-selection
Maestro tests can run on either iPhone or iPad simulators based on tags in the test YAML files. This allows you to test iPad-specific UI layouts and features while maintaining a single test suite.
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
project
Development rules for uni-app projects built with Vue 3 and TypeScript. uni-app is a framework for creating H5 websites, mini-programs, and mobile apps from one codebase.