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.
git 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/analytics-events)<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/analytics-events"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/analytics-events/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.
<a href="https://agentmods.dev/rules/sampaio-tech/flutter-core-modules/analytics-events"><img src="https://agentmods.dev/badge/rules/sampaio-tech/flutter-core-modules/analytics-events.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01013 |
| Opus 5.5 | $0.00000 | $0.00405 |
| Sonnet 5.5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00101 |
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 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.
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:
PascalCaseDart classes- Descriptive of the action or event (not
Event1,Clicked, etc.) - Prefixed with
TapOnfor UI tap events
Property Value Types
Properties map String keys to Object values. Allowed value types:
Stringnum/int/doubleboolMap<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);
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.
- 2mo ago First seen · 147 lines · 0 tokens per session scan A 9bc9cf3fa50a
analytics-events 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 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.