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/upgradenpx skills add strvcom/flutter-template --skill upgradegit 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.00047 | $0.01491 |
| Opus 5 | $0.00023 | $0.00745 |
| Sonnet 5 | $0.00009 | $0.00298 |
| Haiku 4.5 | $0.00005 | $0.00149 |
Grade A, and why
upgrade 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Template Upgrade
Use this skill for SDK and dependency upgrades in this repository.
Read First
AGENTS.mddocs/PROJECT_GUIDELINES.md.fvmrcpubspec.yamlmakefilebuild.yaml.github/workflows/
Upgrade Goals
- Keep
.fvmrcandpubspec.yamlaligned. - Let
pubresolve compatible versions rather than guessing. - Regenerate all generated code after package changes.
- Fix API migrations and lint changes introduced by the newer toolchain.
- Verify local commands and CI still reflect the project pin.
Workflow
- Check current SDK pin in
.fvmrcandpubspec.yaml. - Confirm the target Flutter version.
- Update
.fvmrc. - Activate the new SDK locally — this always needs to happen after changing
.fvmrc:fvm install fvm use <version> fvm global <version>fvm use <version>updates the project SDK, whilefvm global <version>keeps plainfluttercommands from resolving through an older global SDK. - Update
.vscode/settings.json— setdart.flutterSdkPathto.fvm/flutter_sdk. Then restart VSCode (or run "Dart: Change Flutter SDK" from the command palette) so the Dart/Flutter extension reloads against the new SDK. Skipping this causes the IDE to keep analyzing with the old version even though the CLI is already on the new one. - Update
pubspec.yamlenvironment constraints to match the new SDK floor. - Run dependency audit commands such as
fvm flutter pub outdated. - Use
fvm flutter pub upgrade --major-versionswhen the goal is to move the dependency graph forward broadly. - Review any changed direct constraints in
pubspec.yaml. - Run:
fvm flutter pub getmake genfvm flutter analyzefvm flutter test
- Fix breakages from:
- package API changes
- analyzer/lint changes
- build runner or codegen config warnings
- generated native plugin files
- Review GitHub Actions to ensure they still use the pinned project SDK.
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 · 153 lines · 47 tokens per session scan A 094adfbd868c
upgrade is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 1,491 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
speckit-analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
add-sample
Create a SamplesApp sample page with correct theming and attributes. Use when adding UI samples for controls.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…