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/flutter-intellij/remove-platform-versionnpx skills add flutter/flutter-intellij --skill remove-platform-versiongit clone --depth 1 https://github.com/flutter/flutter-intellijWhat 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.00032 | $0.00756 |
| Opus 5 | $0.00016 | $0.00378 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
remove-platform-version 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Remove Platform Version Support
You are tasked with removing support for an older IntelliJ Platform or Android Studio version (e.g., dropping support for 2025.1 / build 251 and raising the lower bound to 2025.2 / build 252).
Objective
Systematically update compatibility ranges, clean up CI verification loops and baseline files, identify and remove obsolete compatibility code or TODOs, check repository issues, and update documentation.
Workflow Instructions
1. Establish Baseline & Identify Target Version
- Identify the build number being removed (e.g.,
251for2025.1) and the new lower bound (e.g.,252for2025.2). - Run
./gradlew testClassesto ensure the project compiles before making changes.
2. Update Compatibility Lower Bound (gradle.properties)
- Open
gradle.properties. - Update
sinceBuild=<version>to the new lower bound build number (e.g., changesinceBuild=251tosinceBuild=252).
3. Update CI Verification Script (tool/github.sh)
- Open
tool/github.sh. - Locate the
VERIFY_BOTverification loop (for version in ...; do). - Remove the dropped version number from the list so that
./gradlew verifyPluginis only run against active versions in the compatibility range.
4. Remove Obsolete Verifier Baseline (tool/baseline/)
- Check
tool/baseline/<version>/for the removed version directory. - Remove the directory and baseline file (e.g., using
git rm -r tool/baseline/<version>) so baseline update scripts (tool/update_baselines.sh) do not attempt to verify unsupported versions.
5. Search & Remove Obsolete Code and TODOs
- Search Codebase: Grep
src/for references to the removed build number or version string (e.g.,251,2025.1). - Check Version Checks: Look for version-specific branches or workarounds (such as in
DartPluginVersion.javaor UI compatibility shims) that check for the removed version and simplify or remove dead code paths. - Check TODOs: Look for comments like
TODO: remove when dropping support for <version>or similar workarounds that can now be cleaned up.
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 · 51 lines · 32 tokens per session scan A 5da7b1090ea0
remove-platform-version is a skill published in the GitHub repository flutter/flutter-intellij (2,013 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 32 tokens to every session and 756 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
flutter-upgrade
Flutter SDKバージョンアップグレード対応。新バージョンのリリースノート・Breaking Changes調査、コードベース影響分析、mise/CI/Shorebird含むプロジェクト全体の対応タスクリスト作成と実行。「Flutterアップグレード」「Flutter X.Y.Zがリリースされた」「Flutter最新化」「Flutter更新」と言われたとき、またはFlutterの新バージョンについて言及されたときに使用する。.
release-bridge
Bridge Server のリリース（バージョンbump + CHANGELOG + タグ → GH Actions で npm publish）.
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
code-review
Use when asked to review a PR, MR, branch, or diff, audit changed files, or check code quality.
architecture-feature-first
Use when creating a feature, designing folder structure, adding repositories/services/view models, wiring dependency injection, or deciding which layer owns logic.