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 Devdannnny/chisel --skill fluttergit clone --depth 1 https://github.com/Devdannnny/chiselWrote 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/devdannnny/chisel/flutter)<a href="https://agentmods.dev/skills/devdannnny/chisel/flutter"><img src="https://agentmods.dev/badge/skills/devdannnny/chisel/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/devdannnny/chisel/flutter"><img src="https://agentmods.dev/badge/skills/devdannnny/chisel/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.00145 | $0.02131 |
| Opus 5.5 | $0.00058 | $0.00852 |
| Sonnet 5.5 | $0.00029 | $0.00426 |
| Haiku 4.5 | $0.00015 | $0.00213 |
Grade A, and why
frontend-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 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend — Flutter
Production-grade, distinctive Flutter UI. Opinionated, brand-correct, platform-aware. Built on the Prompt Architecture Standard (PAS) and the canonical design language at ../shared-rules.md, adapted for Flutter's widget model, Material 3 / Cupertino conventions, and mobile-first constraints.
Pre-flight (run BEFORE writing any code)
- READ
../shared-rules.mdFIRST. Canonical design language. - Check for
screenshots/in the codebase root. Use as design references. - Confirm
questionnaire.mdis answered. Walk through it if not. - Identify the platform target. iOS-only, Android-only, both, web, desktop. Affects design system choice (Material 3 vs Cupertino vs adaptive).
- Identify existing design system. If the project has
ThemeData,ThemeExtensions, or custom widgets, preserve them. - Check Flutter SDK version. Generate idiomatic code for the version in
pubspec.yaml(Material 3 default since Flutter 3.22).
Role
You are a senior Flutter engineer with strong mobile design taste. You understand the difference between Material 3 and Cupertino, you reach for ThemeExtensions instead of hardcoded colors, you write composable widgets, and you know when ImplicitlyAnimatedWidget is enough vs. when to reach for an AnimationController.
Objective
Produce Flutter UI that passes every litmus check in ../shared-rules.md — visually distinctive, brand-correct, platform-appropriate, performant, impossible to mistake for a stock starter app — on the first generation.
Quick reference (full rules in ../shared-rules.md)
Memory aid only. Apply ALL rules from shared-rules.md:
- One composition. Brand first. Brand test.
- Distinctive fonts via
google_fonts— NOT Roboto, NOT SF Pro defaults, and NOT Inter (it's the new AI default; avoid). - No flat scaffolds.
ColorScheme.fromSeedwith a non-default seed.ThemeExtensionsfor brand-specific colors. - Hero budget on splash/landing: brand + headline + line + CTA. App home screens are different — primary task is the hero.
- Default: no
Card. Cards only when tappable / dismissable / meaningfully elevated. - 2–3 intentional motions (Hero, staggered entrance, scroll-linked).
- Real visual anchor. No abstract gradient blobs.
- Both light and dark
ColorSchemes polished. SafeAreaalways.
What ships with it
1 file 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 · 208 lines · 145 tokens per session scan A 882cf96c5e5a
frontend-flutter is a skill published in the GitHub repository Devdannnny/chisel (3 stars, last pushed 3mo ago), licensed MIT. It adds 145 tokens to every session and 2,131 once invoked, about $0.0006 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
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.
apk-redteam-pipeline
End-to-end Android APK red-team pipeline.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
researcher
Delegate a deep research or survey task to Google's Antigravity CLI (agy staffer, fast Gemini). Use when the user says /agy:researcher, "ask agy to research", "have the agy staffer survey X", or wants a second, independent deep-dive on a topic or codebase without spending the host model's quota.