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/strvcom/flutter-template/lint-formatnpx skills add strvcom/flutter-template --skill lint-formatgit clone --depth 1 https://github.com/strvcom/flutter-templateWhat 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.00056 | $0.00669 |
| Opus 5 | $0.00028 | $0.00334 |
| Sonnet 5 | $0.00011 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
lint-format 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 3d 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Lint and Format
MANDATORY
Run this skill after completing Flutter/Dart code changes unless a broader verification skill already ran equivalent checks. Never declare code work complete with known formatting or analyzer failures.
Read First
AGENTS.mddocs/PROJECT_GUIDELINES.mdanalysis_options.yamlpubspec.yaml
Usage
Run the wrapper script from the repo root:
.agents/skills/lint-format/scripts/lint-format.sh
The script auto-detects whether Flutter-relevant files changed. When relevant files changed, it formats changed Dart files and runs a project-wide analyzer pass.
Claude-discovered path:
.claude/skills/lint-format/scripts/lint-format.sh
Flags
| Flag | What it does |
|---|---|
all or --all |
Format standard Dart source directories even if no changed files are detected, then analyze. |
--check |
Check formatting without writing changes, then analyze. |
--format-only |
Run only fvm dart format. |
--analyze-only |
Run only fvm flutter analyze. |
--help |
Show script usage. |
What It Runs
| Step | Command |
|---|---|
| Format | fvm dart format <changed Dart files> |
| Format check | fvm dart format --set-exit-if-changed <changed Dart files> |
| Analyze | fvm flutter analyze |
The default formatter target is changed non-generated Dart files. It skips generated outputs such as *.g.dart, *.freezed.dart, *.gr.dart, and lib/assets/**.
If changed annotations, routes, DTOs, localization, or asset inputs require generated files, run make gen before this skill so the analyzer sees the current generated code.
Feedback Loop
- Run the script.
- If formatting changed files, inspect the diff.
- If analyzer failures appear, fix the underlying source issue.
- Run
make genwhen the failure points to stale generated code. - Re-run the script until all checks pass.
- Only then declare work complete.
Prerequisites
- FVM installed and configured for the repo.
- Dependencies fetched with
fvm flutter pub get. - Generated files are current when the change touched codegen inputs.
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.
- 3d ago First seen · 79 lines · 56 tokens per session scan A 1e225339476b
lint-format is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 669 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…