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/flutter/agent-plugins/dart-build-cli-appnpx skills add flutter/agent-plugins --skill dart-build-cli-appgit clone --depth 1 https://github.com/flutter/agent-pluginsWhat 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.00029 | $0.02111 |
| Opus 5 | $0.00015 | $0.01056 |
| Sonnet 5 | $0.00006 | $0.00422 |
| Haiku 4.5 | $0.00003 | $0.00211 |
Grade A, and why
dart-build-cli-app 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- dart-build-cli-app — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building Dart CLI Applications
Contents
- Project Setup & Architecture
- Argument Parsing & Command Routing
- Execution & Error Handling
- Testing CLI Applications
- Compilation & Distribution
- Workflows
- Examples
Project Setup & Architecture
Initialize new CLI projects using the official Dart template to ensure standard directory structures.
- Run
dart create -t cli <project_name>to scaffold a console application with basic argument parsing. - Place executable entry points (files containing
main()) exclusively in thebin/directory. - Place internal implementation logic in
lib/src/and expose public APIs vialib/<project_name>.dart. - Enforce formatting in CI environments by running
dart format . --set-exit-if-changed. This returns exit code 1 if formatting violations exist.
Argument Parsing & Command Routing
Import the args package to manage command-line arguments, flags, and subcommands.
- If building a simple script: Use
ArgParserdirectly to define flags (addFlag) and options (addOption). - If building a complex, multi-command CLI (like
git): ImplementCommandRunnerand extendCommandfor each subcommand. - Define global arguments on the
CommandRunner.argParserand command-specific arguments on the individualCommand.argParser. - Catch
UsageExceptionto gracefully handle invalid arguments and display the automatically generated help text. - Validate Help Text Accuracy: Ensure the help text provides all necessary information to run the tool. If the help text references a compiled executable name, and the user needs to add it to their PATH to run it that way, provide clear instructions on how to do so in the help text or description.
Execution & Error Handling
Leverage the io and stack_trace packages to build robust, production-ready CLI tools.
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.
- 2d ago First seen · 186 lines · 29 tokens per session scan A 39c82e4ca39f
dart-build-cli-app is a skill published in the GitHub repository flutter/agent-plugins (2,895 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 29 tokens to every session and 2,111 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…