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 migrate-intellij-utilgit 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/migrate-intellij-util)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/migrate-intellij-util"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/migrate-intellij-util.svg" alt="Measured on agentmods" height="20"></a>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.00031 | $0.00558 |
| Opus 5 | $0.00015 | $0.00279 |
| Sonnet 5 | $0.00006 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
migrate-intellij-util 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 7d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: API Migration to use com.intellij.util.* classes and methods
You are tasked with optimizing memory usage, consistency, and performance by migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations.
Objective
Go read https://javadoc.jetbrains.net/teamcity/openapi/current/com/intellij/util/package-summary.html, and then optimize memory usage, consistency, and performance by migrating standard Java/Kotlin classes to IntelliJ's specialized com.intellij.util implementations.
Candidates for Migration
ArrayList->SmartList(for potentially empty/small lists)HashMap/ConcurrentHashMap->ContainerUtilmapsStringmanipulation ->StringUtil(e.g.,isEmpty,join,notNullize)Path/Filestring manipulation ->PathUtiljavax.swing.Timer->Alarm(for UI-related callbacks/debouncing)- Null checks ->
ObjectUtils(e.g.,doIfNotNull,coalesce) - Array resizing/merging ->
ArrayUtil
Workflow Instructions
1. Baseline
- Run
./gradlew testClasses,./gradlew test, and./gradlew verifyPluginto ensure project is in a good state.
2. Select Target
- Identify a single migration opportunity within a single package.
3. Constraint
- Keep the change extremely small (max 50 lines of code change).
4. Migrate
- Replace standard API with the
com.intellij.utilequivalent.
5. Verify
- Run
./gradlew testClassesto ensure migration didn't break test compilation. - Run
./gradlew testand./gradlew verifyPluginto ensure no regressions. - Suggest manual test steps: Check code changes made and write test steps for a user to execute that will trigger changed code paths. If needed, add logging statements to verify code paths have successfully run.
6. Report & Review
- Summarize the migration.
- Test Location: Explicitly state where in the IDE user should go to test changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
- Action: Ask user to review changes closely.
- Do not commit or push.
- Provide a suggested Git commit message (e.g., "Migrate code to use StringUtil in [Class Name]").
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.
- 7d ago First seen · 47 lines · 31 tokens per session scan A ef7252b49cdb
migrate-intellij-util is a skill published in the GitHub repository flutter/flutter-intellij (2,013 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 31 tokens to every session and 558 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
android-navigation-3
Install and migrate to Jetpack Navigation 3. Use when implementing Navigation 3 patterns including NavDisplay, NavKey routes, deep links, multiple backstacks, scenes (dialogs, bottom sheets), or migrating from Navigation 2.
authoring-java-sdk-tasks
Writes Airflow task logic in Java, Kotlin, or any JVM language using the Airflow Java SDK. Use when the user wants to implement Airflow tasks in Java/JVM, asks about @Builder.Dag/@Builder.Task/@Builder.XCom, the Task/BundleBuilder interfaces, reading connections/variables/XComs from Java, the JSON-to-Java type…
signals-migration-6-to-7
Detailed guidelines, patterns, and rules for migrating codebases from signals.dart version 6.x to version 7.x.
null-safety
Use when annotating nullability in Spring Boot 3 / Spring Framework 6 code, integrating Kotlin, or adding static nullability checks without assuming Spring Framework 7 JSpecify defaults.
jackson-3-migration
Migrer Jackson 2.x til Jackson 3.x (tools.jackson) i Kotlin/Java-prosjekter — automatisert OpenRewrite-pass pluss manuell Kotlin-spesifikk opprydding og verifisering.
java-to-kotlin
Trinnvis Java-til-Kotlin-migrering med rammeverk-bevisste transformasjoner for Spring, Ktor og Nav-mønstre.