package-usage

Integration rules for using the flutter_core_modules package inside a Flutter application. They describe the required startup order and providers for services such as Firebase, configuration, storage, and analytics.

In plain words
What is it for?
Use them when setting up the app entry point, initializing Firebase and Remote Config, loading preferences and environment settings, and starting the provider tree.
Why use it?
They prevent initialization-order errors when the app depends on several shared services.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/sampaio-tech/flutter-core-modules/package-usage
Clone the repo
git clone --depth 1 https://github.com/sampaio-tech/flutter-core-modules

Made for: Cursor.

Per session 46 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,728 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00046 $0.01728
Opus 5 $0.00023 $0.00864
Sonnet 5 $0.00009 $0.00346
Haiku 4.5 $0.00005 $0.00173

Measured yesterday against content hash 9626a148cfaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.cursor/rules/package-usage.mdc · 286 lines

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());

Read the full file on GitHub · 286 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. yesterday First seen · 286 lines · 46 tokens per session scan A 9626a148cfaf

Subscribe to this mod's changes

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.