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/package-usagegit clone --depth 1 https://github.com/sampaio-tech/flutter-core-modulesWhat 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.00046 | $0.01728 |
| Opus 5 | $0.00023 | $0.00864 |
| Sonnet 5 | $0.00009 | $0.00346 |
| Haiku 4.5 | $0.00005 | $0.00173 |
Grade A, and why
package-usage 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 yesterday.
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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Package Usage Rules — flutter_core_modules
This document describes how to correctly integrate flutter_core_modules into a consuming Flutter application.
App Initialization Sequence
main() must execute in this exact order:
void main() async {
WidgetsFlutterBinding.ensureInitialized();
// 1. Firebase Core (required for Remote Config, Analytics, Storage, Crashlytics)
await Firebase.initializeApp(options: DefaultFirebaseOptions.currentPlatform);
// 2. Firebase Remote Config (gates analytics provider initialization)
final remoteConfig = await FirebaseRemoteConfigCore.init();
// 3. SharedPreferences singleton (required before any provider reads it)
await SharedPreferencesInstance.getInstanceSharedPreferences();
// 4. DotEnv.init() — loads .env + initializes all analytics SDKs + RevenueCat
await DotEnv.init(remoteConfig);
// 5. Optional: HTTP override for dev certificate bypass
// HttpOverrides.global = CertificateHttpOverrides();
// 6. App entry with ProviderScope
runApp(
ProviderScope(
child: MyApp(),
),
);
}
Critical: DotEnv.init() must receive the already-initialized FirebaseRemoteConfig instance because analytics providers check Remote Config flags before initializing.
Required .env File
The .env file must be present in the app root and listed in pubspec.yaml assets. Keys used by this package:
# Analytics (all optional — omit to disable that provider)
STATSIG_CLIENT_SDK_KEY=client-...
MIXPANEL_TOKEN=...
POSTHOG_TOKEN=phc_...
AMPLITUDE_TOKEN=...
CLARITY_PROJECT_ID=...
# Revenue (required if using revenue feature)
REVENUECAT_PROJECT_APPLE_API_KEY=appl_...
REVENUECAT_PROJECT_GOOGLE_API_KEY=goog_...
Theme Setup
Use ThemeStateNotifier to persist and apply theme across sessions:
// In your app widget:
final themeData = ref.watch(themeStateNotifierProvider);
IosTheme(
data: themeData ?? IosLightThemeData(), // default to light
child: MyApp(),
)
To toggle theme from settings:
// Reads state, saves to SharedPreferences, updates provider:
ref.read(themeStateNotifierProvider.notifier).setThemeData(iosThemeData: IosDarkThemeData());
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.
- yesterday First seen · 286 lines · 46 tokens per session scan A 9626a148cfaf
package-usage is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 1,728 once invoked, about $0.0002 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 cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
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.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.