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/yendangn/flutter-app-builder/flutter-design-systemnpx skills add yendangn/flutter-app-builder --skill flutter-design-systemgit 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-design-system)<a href="https://agentmods.dev/skills/yendangn/flutter-app-builder/flutter-design-system"><img src="https://agentmods.dev/badge/skills/yendangn/flutter-app-builder/flutter-design-system.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.00064 | $0.00634 |
| Opus 5 | $0.00032 | $0.00317 |
| Sonnet 5 | $0.00013 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
flutter-design-system 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 5d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Design System
Full reference: template.md
Key rules
- Figma → JSON → Dart token pipeline: export design tokens from Figma Style Dictionary → run codegen → output
app_colors.dart,app_spacing.dart,app_typography.dart. Tokens are the single source of truth. ThemeExtension<T>for brand-specific tokens thatThemeDatadoesn't cover natively (custom semantic colors, brand radius, etc.).- Widgetbook: one
@WidgetbookUseCaseper component variant. Knobs for all configurable properties. - Golden tests: one golden per component state (default, hover, disabled, error). Run
flutter test --update-goldenswhen intentional visual changes happen. - Component governance: new shared widgets require a Widgetbook entry + golden test before merging.
- Multi-brand: separate
AppConfig.brandenum drives whichThemeExtensionvalues are loaded. Swap at runtime without rebuilding. - Never hardcode brand-specific colors in components — read from
Theme.of(context).extension<BrandTokens>().
BrandTokens interface
@immutable
class BrandTokens extends ThemeExtension<BrandTokens> {
const BrandTokens({
required this.accentPrimary,
required this.accentSecondary,
required this.surfaceBrand,
required this.borderRadius,
required this.brandName,
});
final Color accentPrimary;
final Color accentSecondary;
final Color surfaceBrand;
final double borderRadius;
final String brandName;
@override
BrandTokens copyWith({...}) => BrandTokens(...);
@override
BrandTokens lerp(BrandTokens? other, double t) => BrandTokens(
accentPrimary: Color.lerp(accentPrimary, other?.accentPrimary, t)!,
// ...
);
}
Usage in widgets:
final brand = Theme.of(context).extension<BrandTokens>()!;
Container(color: brand.accentPrimary, ...);
Files
tools/token_export/ ← Figma export + codegen scripts
lib/src/app/theme/
brand_tokens.dart ← ThemeExtension<BrandTokens>
widgetbook/ ← Widgetbook app (separate package or flavored entry)
test/goldens/ ← component golden images
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.
- 5d ago First seen · 75 lines · 64 tokens per session scan A 016afa56624c
flutter-design-system is a skill published in the GitHub repository yendangn/flutter-app-builder (5 stars, last pushed 2mo ago), licensed MIT. It adds 64 tokens to every session and 634 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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…