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/feature-reviewgit 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/rules/sampaio-tech/flutter-core-modules/feature-review)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/feature-review"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-review.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.00000 | $0.00980 |
| Opus 5 | $0.00000 | $0.00490 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
Grade A, and why
feature-review 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Review — Rules
What Is Already Implemented — Check Before Building
| Capability | Status |
|---|---|
| Native in-app review dialog | ✅ InAppReviewStateNotifier.requestReview() |
| Review availability check | ✅ InAppReviewStateNotifier.isAvailable() |
| Open App Store / Play Store listing | ✅ InAppReviewStateNotifier.openStoreListing() |
| Email feedback with auto-subject | ✅ LaunchFeedbackStateNotifier.launch() |
| Feedback email from Remote Config | ✅ FirebaseRemoteConfigCore.feedbackEmail (key: feedback_email) |
| Analytics events for review/feedback | ✅ TapOnReviewButton, TapOnFeedbackButton, InAppReviewIsAvailable |
| Custom review request timing / frequency | ❌ Not in package — OS-controlled; implement logic in consuming app |
Before building review or feedback flows, confirm whether the above already covers the requirement.
Layer Structure
lib/src/features/review/
├── domain/
│ ├── repositories/in_app_review_repository.dart
│ └── usecases/ (IsAvailableUsecase, RequestReviewUsecase, OpenStoreListingUsecase)
├── data/
│ └── repositories/in_app_review_repository.dart # InAppReviewRepositoryImpl
└── presentation/
├── providers/in_app_review.dart # inAppReviewProvider (SDK instance)
├── config/launch_url.dart # canLaunchFeedback / launchFeedback
└── notifiers/
├── in_app_review_state_notifier.dart # state: bool (is available)
└── launch_feedback_state_notifier.dart # state: bool (can launch)
Correct Usage Patterns
Request in-app review with analytics
await ref.read(inAppReviewStateNotifierProvider.notifier).requestReview(
requestReviewCallback: () => TapOnReviewButton().track(context: context),
isAvailableCallback: (isAvailable) =>
InAppReviewIsAvailable(isAvailable: isAvailable).track(context: context),
);
Check availability before showing a "Rate App" button
// On widget mount:
useSafeEffect(() {
ref.read(inAppReviewStateNotifierProvider.notifier).isAvailable();
return () {};
}, []);
// In build:
final canReview = ref.watch(inAppReviewStateNotifierProvider);
if (canReview) { /* show button */ }
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 · 117 lines · 0 tokens per session scan A 73b4c7256a85
feature-review is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 980 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
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.
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.
swift
Swift patterns: SwiftUI, actors, async/await, value types.