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 ariaramin/flutter-skills --skill lottie-fluttergit clone --depth 1 https://github.com/ariaramin/flutter-skillsWrote 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/ariaramin/flutter-skills/lottie-flutter)<a href="https://agentmods.dev/skills/ariaramin/flutter-skills/lottie-flutter"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/lottie-flutter/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/skills/ariaramin/flutter-skills/lottie-flutter"><img src="https://agentmods.dev/badge/skills/ariaramin/flutter-skills/lottie-flutter.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.00058 | $0.15448 |
| Opus 5.5 | $0.00023 | $0.06179 |
| Sonnet 5.5 | $0.00012 | $0.03090 |
| Haiku 4.5 | $0.00006 | $0.01545 |
Grade A, and why
lottie-flutter 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 — 1,917 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lottie for Flutter
Purpose
This skill provides exhaustive, source-grounded operating instructions for an autonomous AI coding agent implementing, refactoring, optimizing, and reviewing Lottie animations within Flutter applications. It codifies the architecture of the pure Dart lottie runtime (lottie: ^3.5.1), establishes strict composition lifecycle and resource ownership models, enforces multi-platform rendering efficiency across Impeller and CanvasKit/Wasm, and prevents performance, memory, and ticker leaks.
When to Use This Skill
Activate this skill whenever a task involves:
- Adding, updating, or styling Lottie animations in Flutter.
- Integrating
AnimationControllerwithLottiecompositions, progress scrubbing, or marker-based playback. - Dynamically altering animation colors, strokes, opacity, text, or paths via
ValueDelegateandLottieDelegates. - Loading animations from assets, network URLs, files, memory bytes,
.zipbundles,.tgs(Telegram stickers), or.lottie(dotLottie) containers. - Optimizing frame rates, repaint boundaries, CPU/GPU overhead, and memory consumption in animated UIs.
- Embedding animations inside virtualized scroll views (
ListView,GridView,CustomScrollView). - Designing reusable, accessible, and theme-adaptive design system animation components.
- Diagnosing jank, raster thread delays, unhandled composition exceptions, or memory leaks.
Source of Truth
Primary authoritative sources:
- Official Flutter Lottie Package:
https://pub.dev/packages/lottie(Current stable:3.5.1, maintained byxaha.dev, GitHub:xvrh/lottie-flutter). - Official Package API Reference:
https://pub.dev/documentation/lottie/latest/lottie/lottie-library.html. - Official GitHub Repository & Examples:
https://github.com/xvrh/lottie-flutter/tree/master/example. - LottieFiles Specification & Best Practices:
https://lottiefiles.comandhttps://github.com/airbnb/lottie-spec.
When implementation decisions conflict, apply the following precedence hierarchy:
- Official
lottieDart package API and behavior (v3.5.1). - Official repository sample code and test suites (
xvrh/lottie-flutter). - Flutter framework lifecycle, rendering, and accessibility contracts.
- LottieFiles format specifications and motion design best practices.
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 · 1,917 lines · 58 tokens per session scan A 49071cd8b501
lottie-flutter is a skill published in the GitHub repository ariaramin/flutter-skills (6 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 15,448 once invoked, about $0.0002 per session on Opus 5.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-10-11.
Other skills, from other repositories
potpie-debug-memory
Use while debugging or troubleshooting failures, flaky tests, incidents, production alerts, CI failures, local dev setup issues, repeated bugs, prior fixes, failed attempts, and verification history.
speq-audit
Audit a speq project's health — spec-library structure, feature/decision-log/plan validation, ADR noise, mission-to-spec sync, unrecorded plans, and gitignore hygiene — then guide fixes. Use when the user asks to audit, health-check, doctor, lint, or sanity-check the specs or repo, or after cloning or inheriting a…
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
diagnose-with-memory
A bug-diagnosis workflow that uses records of earlier failures, decisions, and lessons. It checks whether past findings still apply to the current version and environment before investigating the code.
systematic-debug
4-phase root-cause debugging — reproduce, isolate, fix, verify. Triggers on hard bug, can't figure out, intermittent, keeps failing, root cause.
debug
Diagnose and fix bugs, errors, crashes. Triggers on fix, bug, error, crash, broken, failing requests.