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 skills/sampaio-tech/flutter-core-modules/analytics-featurenpx skills add sampaio-tech/flutter-core-modules --skill analytics-featuregit 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/skills/sampaio-tech/flutter-core-modules/analytics-feature)<a href="https://agentmods.dev/skills/sampaio-tech/flutter-core-modules/analytics-feature"><img src="https://agentmods.dev/badge/skills/sampaio-tech/flutter-core-modules/analytics-feature.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.00080 | $0.02450 |
| Opus 5 | $0.00040 | $0.01225 |
| Sonnet 5 | $0.00016 | $0.00490 |
| Haiku 4.5 | $0.00008 | $0.00245 |
Grade A, and why
analytics-feature 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 3d 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 — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Feature — flutter_core_modules
The analytics feature provides a provider-agnostic event tracking API. A single EventEntity.track(context) call fans out to all enabled analytics providers simultaneously.
1. Architecture Overview
EventEntity.track(context)
│
└──► ProviderScope.containerOf(context)
│
└──► analyticsRepositoryProvider (AnalyticsRepositoryImpl)
│
├──► AmplitudeConfig.enabled → amplitude.track(BaseEvent)
├──► FirebaseAnalyticsConfig.enabled → firebaseAnalytics.logEvent()
├──► PosthogConfig.enabled → posthog.capture()
├──► MixpanelConfig.enabled → mixpanel.track()
└──► StatsigConfig.enabled → Statsig.logEvent()
Each provider runs as a Future.microtask with .catchError(() {}) — failures in one provider never affect others.
2. EventEntity — Base Class for All Events
File: lib/src/features/analytics/domain/entities/events/event_entity.dart
abstract class EventEntity {
const EventEntity();
// Override to provide event properties
Map<String, Object>? get properties;
// Derived — converts class name to snake_case automatically
// e.g. TapOnReviewButton → 'tap_on_review_button'
String get name => formatToSnakeCase(runtimeType.toString());
// Tracks to all enabled analytics providers via ProviderScope
Future<void> track({required BuildContext context});
// Properties with all values toString'd (needed for Firebase which rejects non-String/num)
Map<String, Object>? get propertiesToAvoidAssertInputTypes;
}
Key design decision: Event names are derived automatically from the class name via runtimeType.toString() converted to snake_case. No manual name override needed.
3. How to Define a New Event
Simple event (no properties):
// In the relevant file or a new events file:
class TapOnMyFeature extends EventEntity {
const TapOnMyFeature();
@override
Map<String, Object>? get properties => const {};
}
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.
- 3d ago First seen · 286 lines · 80 tokens per session scan A efe2c95a2e1c
analytics-feature is a skill published in the GitHub repository sampaio-tech/flutter-core-modules (2 stars, last pushed 11d ago), licensed MIT. It adds 80 tokens to every session and 2,450 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…