feature-review

feature-review is a cursor rule for Cursor from sampaio-tech/flutter-core-modules. It costs 0 tokens per session (980 once invoked), scanned A, original, MIT.

A set of development rules for review and feedback features in a Flutter package, including in-app store reviews and feedback email.

In plain words
What is it for?
Building or checking review requests, store-listing links, feedback emails, remote configuration, analytics, and related Flutter code.
Why use it?
It shows which review capabilities already exist and which decisions belong in the application using the package.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Building or checking review requests, store-listing links, feedback emails, remote configuration, analytics, and related Flutter code.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/sampaio-tech/flutter-core-modules/feature-review
Install

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.

Clone the repo
git clone --depth 1 https://github.com/sampaio-tech/flutter-core-modules

Made for: Cursor.

Wrote 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.

agentmods badge for feature-review

README.md
[![agentmods](https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-review/github.svg)](https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/feature-review)
Your own site
<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for feature-review

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 980 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00980
Opus 5.5 $0.00000 $0.00392
Sonnet 5.5 $0.00000 $0.00196
Haiku 4.5 $0.00000 $0.00098

Measured 2mo ago against content hash 73b4c7256a85, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.cursor/rules/feature-review.mdc · 117 lines

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 */ }

Read the full file on GitHub · 117 lines

Changes

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.

  1. 2mo ago First seen · 117 lines · 0 tokens per session scan A 73b4c7256a85

Subscribe to this mod's changes

feature-review is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 16d 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.