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/release-preparenpx skills add strvcom/flutter-template --skill release-preparegit 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.00045 | $0.00446 |
| Opus 5 | $0.00023 | $0.00223 |
| Sonnet 5 | $0.00009 | $0.00089 |
| Haiku 4.5 | $0.00005 | $0.00045 |
Grade A, and why
release-prepare 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.
What it actually says
Flutter Template Release Prepare
Use this skill when preparing a release branch and PR in this repository.
Read First
AGENTS.mddocs/PROJECT_GUIDELINES.mdREADME.mdpubspec.yamlrelease_notes.txt
Goal
This skill is for the pre-build release phase.
It should:
- update the app version
- update
release_notes.txt - create or prepare a branch named
release/<version> - prepare the release PR
It should not:
- create Android release tags yet
- build Android release artifacts yet
- build iOS IPA files yet
Release builds happen only after the release PR is merged.
Workflow
- Confirm the target release version.
- Update
pubspec.yamlto that version. - Add a matching release-notes section to
release_notes.txt. - Verify that the release branch should be named
release/<version>. - Create or switch to
release/<version>. - Run:
make genif required by any included changesfvm flutter analyzefvm flutter test
- Prepare the PR targeting the team’s release base branch.
- Only after the PR is merged should release builds or release tags be created.
Watch Outs
- Do not create Android tags during the prepare phase.
- Do not build iOS IPA files during the prepare phase.
- Keep release notes consistent with the actual shipped changes.
- If the branch target differs from the repo defaults documented in
README.md, follow the actual team process.
Completion Criteria
- version updated
- release notes updated
- branch named
release/<version> - PR is ready for review or merge
- no build or tag steps were mixed into this phase
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 · 60 lines · 45 tokens per session scan A 9b8c18c812d0
release-prepare is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 446 once invoked, about $0.0002 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…