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 tienenwu/fables --skill fluttergit clone --depth 1 https://github.com/tienenwu/fablesWrote 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/tienenwu/fables/flutter)<a href="https://agentmods.dev/skills/tienenwu/fables/flutter"><img src="https://agentmods.dev/badge/skills/tienenwu/fables/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/tienenwu/fables/flutter"><img src="https://agentmods.dev/badge/skills/tienenwu/fables/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.00096 | $0.01330 |
| Opus 5.5 | $0.00038 | $0.00532 |
| Sonnet 5.5 | $0.00019 | $0.00266 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
flutter-dev-playbook 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 1mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🌐 繁體中文（canonical） · English mirror
Flutter Development Judgment Handbook
Core Principles
- A green light in Debug (JIT) does not count: release/profile are AOT-compiled and behave differently from debug —
assertis stripped, tree shaking removes symbols only referenced via reflection/strings, and faster timing shakes out races. Every release-related change and all performance measurement must be verified in profile/release; see references/platform-build.md. build()is a pure function and may be called every frame: never do IO, network,setState, controller construction, or file writes inside build — side effects rerun every frame.- Classify state first: ephemeral vs app state: only this widget uses it and losing it is fine →
setState; shared across widgets or must survive → provider/Bloc. Wrong layer = rebuild storm or lost state. - Actively narrow rebuild scope: read state as low as possible; use
select/Consumerto sink down to the leaf that actually uses the value, so the whole subtree doesn't rebuild along with it. - Two platforms are two engineering efforts: permission declarations, signing, build mode, and plugin native implementations exist once each for Android and iOS; a release only counts as verified when each has been run once.
Kickoff Routing
| Situation | Path | Read first |
|---|---|---|
| New screen/feature | Decide the state owner and layering first, then write widgets | references/state-architecture.md |
| Choose setState / Riverpod / Bloc | Walk the selection decision tree, not personal taste | references/state-architecture.md §1 |
| UI jank / dropped frames / too many rebuilds | Profile first, don't change code first | references/widgets-performance.md §jank |
| Extract widget, const, ListView | Criteria are here; don't extract helper methods blindly | references/widgets-performance.md |
| Touching native (camera/Bluetooth/system API) | First ask whether an existing plugin works | references/platform-build.md §channel |
| Fine in debug, crashes only in release | Assume tree shaking / AOT / environment difference first | references/platform-build.md §build-mode-differences |
| Shipping release / store submission | Run the checklist item by item, once per platform | references/release-checklist.md |
| Adding a dependency | Check pub.dev score and maintenance status first | references/release-checklist.md §packages |
What ships with it
5 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.
- 1mo ago First seen · 59 lines · 96 tokens per session scan A 3e6ae00011c9
flutter-dev-playbook is a skill published in the GitHub repository tienenwu/fables (4 stars, last pushed 2mo ago), licensed MIT. It adds 96 tokens to every session and 1,330 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.
compose-performance
Use when investigating Jetpack Compose recomposition cost, compiler stability reports, skippability, unstable parameters, frame-rate State reads, cross-phase snapshot back-writing, or @ReadOnlyComposable contracts.
Debroid CLI Debugger
Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.
extract-apk
A workflow for finding an Android app on a connected device, exporting its APK, and turning it into searchable decompiled source files. An APK is the installable package used by Android apps.