analytics-events

Rules for defining analytics events in Flutter: named records of user or app actions, with optional data attached to them.

In plain words
What is it for?
Use them when creating event classes or calling the analytics tracking method, especially for UI taps and events with properties.
Why use it?
They prevent inconsistent event names, unsupported property values, and tracking code that does not follow the project’s required structure.

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/analytics-events
Clone the repo
git clone --depth 1 https://github.com/sampaio-tech/flutter-core-modules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,013 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.00000 $0.01013
Opus 5 $0.00000 $0.00507
Sonnet 5 $0.00000 $0.00203
Haiku 4.5 $0.00000 $0.00101

Measured 2d ago against content hash 9bc9cf3fa50a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

analytics-events 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 2d 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/analytics-events.mdc · 147 lines

How it starts

The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Analytics Event Rules — flutter_core_modules

EventEntity Subclass Structure

All analytics events are Dart classes extending EventEntity:

// Minimum required shape
class MyEvent extends EventEntity {
  const MyEvent();

  @override
  Map<String, Object>? get properties => const {};
}

// With properties
class MyEventWithData extends EventEntity {
  final String itemId;
  final double amount;

  const MyEventWithData({required this.itemId, required this.amount});

  @override
  Map<String, Object>? get properties => {
    'item_id': itemId,
    'amount': amount,
  };
}

Event Naming — Automatic from Class Name

Do NOT override name. The event name is derived automatically from runtimeType.toString() converted to snake_case:

TapOnReviewButton       → 'tap_on_review_button'
ChangeLanguageTo        → 'change_language_to'
OnSyncPurchasesCallback → 'on_sync_purchases_callback'

Class names must be:

  • PascalCase Dart classes
  • Descriptive of the action or event (not Event1, Clicked, etc.)
  • Prefixed with TapOn for UI tap events

Property Value Types

Properties map String keys to Object values. Allowed value types:

  • String
  • num / int / double
  • bool
  • Map<String, Object> (nested)
  • List<Object> (items must also be one of these types)
// CORRECT
@override
Map<String, Object>? get properties => {
  'plan_id': planId,        // String
  'price': price,           // double
  'is_annual': isAnnual,    // bool
  'locale': {               // nested Map
    'languageCode': locale.languageCode,
  },
};

// WRONG — avoid nullable values in properties map
@override
Map<String, Object>? get properties => {
  'value': maybeNull ?? 'unknown', // use conditional inclusion instead
};

// CORRECT — conditionally include nullable values
@override
Map<String, Object>? get properties => {
  if (label != null) 'label': label!,
  if (title != null) 'title': title!,
};

Tracking Events

// From BuildContext (widget or static method):
MyEvent().track(context: context);

// With properties:
MyEventWithData(itemId: 'abc', amount: 9.99).track(context: context);

Read the full file on GitHub · 147 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. 2d ago First seen · 147 lines · 0 tokens per session scan A 9bc9cf3fa50a

Subscribe to this mod's changes

analytics-events is a cursor rule published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,013 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.