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 skills add yendangn/flutter-app-builder --skill flutter-analyticsgit clone --depth 1 https://github.com/yendangn/flutter-app-builderWrote 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/yendangn/flutter-app-builder/flutter-analytics)<a href="https://agentmods.dev/skills/yendangn/flutter-app-builder/flutter-analytics"><img src="https://agentmods.dev/badge/skills/yendangn/flutter-app-builder/flutter-analytics.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.1 | $0.00065 | $0.00602 |
| Opus 5 | $0.00032 | $0.00301 |
| Sonnet 5 | $0.00013 | $0.00120 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
flutter-analytics 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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Analytics
Full reference: template.md
Key rules
- Two interfaces:
AnalyticsService(events, screen views, user properties) andCrashReporter(exceptions, breadcrumbs). - Never import
firebase_analytics,firebase_crashlytics, orsentry_flutteroutside their*_impl.dartfiles. - Auto screen tracking: wire a
NavigatorObserver(or GoRouterobservers) that callsanalyticsService.trackScreen()on route change. - Auto state tracking: in
AppBlocObserver.onTransition(), callanalyticsService.trackEvent('state_change', ...). - Forward
AppBlocObserver.onError()tocrashReporter.recordError(). - Enable analytics in prod only — guard with
AppConfig.env.isProd(or enable in uat for QA). - Call
analyticsService.setUserId(id)when the user's identity becomes available (e.g., after profile fetch). CallanalyticsService.reset()on logout — this clears user ID, properties, and session.
AnalyticsService interface
abstract interface class AnalyticsService {
Future<void> trackEvent(String name, {Map<String, Object>? params});
Future<void> trackScreen(String name, {Map<String, Object>? params});
Future<void> setUserId(String? id);
Future<void> setUserProperty({required String key, required String value});
Future<void> reset();
}
Lifecycle wiring pattern
// In AuthCubit — called when auth status changes
case AuthStatus.authenticated:
analyticsService.trackEvent('user_signed_in');
// setUserId called separately from ProfileCubit once user data is loaded
case AuthStatus.unauthenticated:
analyticsService.reset(); // clears userId + properties
// In feature cubits — after key user actions
analyticsService.trackEvent('task_created', params: {'title': title});
Files
lib/src/core/analytics/
analytics_service.dart ← interface (trackEvent, trackScreen, setUserId, setUserProperty, reset)
analytics_service_impl.dart ← Firebase Analytics impl
crash_reporter.dart ← interface (recordError, addBreadcrumb)
crash_reporter_impl.dart ← Firebase Crashlytics impl
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 6d ago First seen · 62 lines · 65 tokens per session scan A 3cbd8b1aed3d
flutter-analytics is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 65 tokens to every session and 602 once invoked, about $0.0003 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…