Flutter Plugin for IntelliJ is an IntelliJ plugin that adds support for developing Flutter applications, which can run on iOS, Android, and the web. It is used by Flutter developers working in IntelliJ IDEA or Android Studio.
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 skills add flutter/flutter-intellij --skill release-plugingit clone --depth 1 https://github.com/flutter/flutter-intellijWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/flutter/flutter-intellij/release-plugin)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/release-plugin"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/release-plugin/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/flutter/flutter-intellij/release-plugin"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/release-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What 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.1 | $0.00030 | $0.01016 |
| Opus 5.5 | $0.00012 | $0.00406 |
| Sonnet 5.5 | $0.00006 | $0.00203 |
| Haiku 4.5 | $0.00003 | $0.00102 |
Grade A, and why
release-plugin scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Update `dartPluginVersion` to the latest public Dart plugin release version. Fetch the latest version from JetBrains Marketplace (e.g. via `curl -s "https://plugins.jetbrains.com/api/plugins/6351/updates?size=1" | jq - How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Release Plugin
You are tasked with preparing a new version release of the flutter-intellij plugin (e.g., releasing 95.0.0).
Objective
Systematically update plugin dependencies, compatibility parameters, and CHANGELOG.md, verify tests and plugin structure, and build the release zip artifact.
Workflow Instructions
1. Update Platform & Dependency Parameters
gradle.properties:- Update
dartPluginVersionto the latest public Dart plugin release version. Fetch the latest version from JetBrains Marketplace (e.g. viacurl -s "https://plugins.jetbrains.com/api/plugins/6351/updates?size=1" | jq -r '.[0].version'or by checking JetBrains Marketplace Dart Plugin) and setdartPluginVersioningradle.propertiesto that version (e.g.,dartPluginVersion= 508.0.0). - If dropping support for older platform versions, update
sinceBuildto the new lower bound (e.g.,sinceBuild=252). Note:untilBuildis omitted for open-ended platform compatibility.
- Update
- New Platform Version Compatibility & Baselines:
- When supporting/verifying a new platform release (e.g., IntelliJ 2026.3 / build
263):- Update the verification loop in
tool/github.sh(for version in ...; do). - Run
./tool/update_baselines.shto generate or update the plugin verifier baseline files intool/baseline/<version>/verifier-baseline.txt.
- Update the verification loop in
- When supporting/verifying a new platform release (e.g., IntelliJ 2026.3 / build
- JxBrowser License Key:
- Ensure
resources/jxbrowser/jxbrowser.propertiesis present (copy from local environment if creating a new git worktree).
- Ensure
2. Fix API & Dependency Compatibility
- Check for compilation errors or API signature changes introduced by the updated dependencies (e.g., websocket/DTD exception handling changes in
FlutterInitializer.javaandFlutterApp.java). - Run
./gradlew testClassesto confirm the codebase compiles against updated dependencies.
3. Update Changelog (CHANGELOG.md)
- Compatibility Changes PR:
- Document compatibility updates under
### ChangedinCHANGELOG.mdwith the PR reference (e.g.,- Removed upper build constraint (\untilBuild`) for open-ended platform compatibility. (#9063)`).
- Document compatibility updates under
- Release Version Bump:
- Rename
## Unreleasedto## <VERSION>.0.0(e.g.,## 95.0.0). - Ensure all user-facing changes since the last release are categorized and tagged with PR numbers.
- Insert a fresh empty
## Unreleasedblock at the top with:## Unreleased ### Added ### Changed ### Removed ### Fixed
- Rename
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.
- 1mo ago First seen · 66 lines · 30 tokens per session scan A 75397a48ce2b
release-plugin is a skill published in the GitHub repository flutter/flutter-intellij (2,019 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 30 tokens to every session and 1,016 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
publish-notes
Draft user-facing release notes, store changelogs, and internal publish summaries.
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
update-site-for-release
Update/publish the Apache Tika website (tika-site SVN repo) for a release — step 17 of the Release Process. Handles the 4.x track (Changes page + aggregate javadoc + Antora docs branch) vs the 3.x maintenance track (full per-version apt docs + javadoc). Use for "update the site", "publish the site for X.Y.Z", "the…
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
shipping-and-launch
Pre-deploy hygiene for a Spring Boot 4 feature — verify gates, capture rollback plan, sign off observability, generate release notes, and stage the rollout. Used by /ship after /review approves the diff. The agent never deploys; it produces the plan a human executes.
zb-release-pipeline
Generate a GitHub Actions pipeline that builds a zb (Zero Dependencies Builder) project and publishes a GitHub Release with the produced JAR. Use whenever the user wants CI/CD, a build pipeline, a release workflow, or GitHub Actions for a zb-based Java project — phrases like "set up GitHub Actions for this zb…