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/build-verifynpx skills add strvcom/flutter-template --skill build-verifygit 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.00107 | $0.01567 |
| Opus 5 | $0.00053 | $0.00783 |
| Sonnet 5 | $0.00021 | $0.00313 |
| Haiku 4.5 | $0.00011 | $0.00157 |
Grade A, and why
build-verify 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.
How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build Verify
Run the full verification suite once after all implementation work is done. This replaces per-task verification — the implementation flow is uninterrupted and centralizes all build / test / analyze / format checks here.
Usage
Run the orchestrator script:
.claude/skills/build-verify/scripts/verify.sh
It runs the Dart phase (codegen + analyze + test) sequentially with fail-fast, then
runs the iOS and Android native builds in parallel, then dart format once
both have passed.
By default the script auto-scopes based on what changed (committed vs ${BASE_REF:-main}
plus uncommitted). Auto-scoping skips irrelevant work so small, single-platform changes
aren't forced to build everything:
| Diff shape | Auto-behavior |
|---|---|
All changes under ios/ only |
Skip Android native build |
All changes under android/ only |
Skip iOS native build |
All changes under test/ only |
Skip both native builds |
| No annotation- or pubspec-relevant changes | Skip make gen codegen |
| Mixed, empty, or no diff | Run everything |
The auto-scope decision is printed at the top of the run so it's never silent.
Flags
| Flag | What it does |
|---|---|
--full |
Disable auto-scoping — run everything regardless of diff |
--skip-gen |
Explicitly skip make gen (assume codegen is current — also disables auto-scope) |
--skip-builds |
Skip native iOS + Android builds (only run Dart phase + format) |
--ios-only |
Run only the iOS native build (still runs Dart phase; also disables auto-scope) |
--android-only |
Run only the Android native build (still runs Dart phase; also disables auto-scope) |
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.
- 2d ago First seen · 135 lines · 107 tokens per session scan A c5f2235115c4
build-verify is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 1,567 once invoked, about $0.0005 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…