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-revenuegit 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-revenue)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/feature-revenue"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/feature-revenue.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.01120 |
| Opus 5 | $0.00000 | $0.00560 |
| Sonnet 5 | $0.00000 | $0.00224 |
| Haiku 4.5 | $0.00000 | $0.00112 |
Grade A, and why
feature-revenue 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature: Revenue — Rules
What Is Already Implemented — Check Before Building
| Capability | Status |
|---|---|
| RevenueCat SDK init (iOS + Android) | ✅ initPlatformState() — called by DotEnv.init() |
| Fetch customer info | ✅ GetCustomerInfoUsecase / notifier.get() |
| Reactive premium status | ✅ isPremiumCustomerProvider — a Provider<bool> |
| Real-time subscription listener | ✅ notifier.listen() / auto-disposed on dispose() |
| Present paywall UI | ✅ notifier.presentPaywall() |
| Full paywall flow with analytics | ✅ presentPaywallForwarded() |
| Sync purchases with store | ✅ SyncPurchasesUsecase |
| Invalidate RevenueCat cache | ✅ InvalidateCustomerInfoCacheUsecase |
| Get RevenueCat user ID | ✅ GetAppUserIdUsecase |
| Check anonymous status | ✅ GetIsAnonymousUsecase |
| Custom paywall UI | ❌ Not in package — uses RevenueCat's built-in UI only |
| Entitlement-specific checks | ❌ Not in package — use customerInfo.entitlements.active directly |
Before adding payment/subscription code, check if the above already covers the requirement.
Layer Structure
lib/src/features/revenue/
├── domain/
│ ├── repositories/revenue_repository.dart
│ └── usecases/ (7 use cases)
├── data/
│ └── repositories/revenue_repository.dart # RevenueRepositoryImpl
└── presentation/
├── config/
│ ├── revenue_cat.dart # initPlatformState()
│ └── functions.dart # presentPaywallForwarded()
└── notifiers/customer_info/
└── customer_info_state_notifier.dart # CustomerInfoStateNotifier + isPremiumCustomerProvider
Correct Usage Patterns
App initialization (already handled)
// DotEnv.init() already calls initPlatformState() — do NOT call it again
await DotEnv.init(remoteConfig);
Fetch + listen on app start
// Call this once on root widget mount (e.g., useSafeEffect):
final notifier = ref.read(customerInfoStateNotifierProvider.notifier);
await notifier.get(); // initial fetch
await notifier.listen(); // register real-time SDK listener
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 · 144 lines · 0 tokens per session scan A 629ec0e8953b
feature-revenue 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 1,120 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
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.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.