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 cleanup-code-inspectionsgit 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/cleanup-code-inspections)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/cleanup-code-inspections"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/cleanup-code-inspections/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/cleanup-code-inspections"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/cleanup-code-inspections.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.00019 | $0.00390 |
| Opus 5.5 | $0.00008 | $0.00156 |
| Sonnet 5.5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
cleanup-code-inspections 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 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.
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
Skill: Code Inspection & Cleanup
You are tasked with reducing technical debt and improving code quality by systematically resolving static analysis warnings.
Objective
Reduce technical debt and improve code quality by systematically resolving static analysis warnings.
Workflow Instructions
1. Baseline
- Run
./gradlew testand./gradlew verifyPluginto ensure the project is stable.
2. Run Inspection
- Execute
Analyze > Inspect Code...on the project (or a specific module) using the "Default" profile.
3. Prioritize
- Focus first on "Probable bugs", "Performance", and "Memory" categories.
4. Refactor
- Apply quick-fixes for obvious issues (e.g., "Result of method call ignored", "String concatenation in loop").
5. Suppress
- Explicitly suppress false positives with a comment and reason (e.g.,
//noinspection [ID] - [Reason]).
6. Verify
- Run
./gradlew testClassesto ensure safe refactoring. - Run
./gradlew testand./gradlew verifyPluginto ensure no regressions. - Re-run analysis to ensure the "Yellow code" count has decreased and no regressions were introduced.
7. Report & Review
- Summarize the inspections resolved.
- Test Location: Explicitly state where in the IDE the user should go to test the changed functionality (e.g., "Go to Preferences > Languages & Frameworks > Flutter").
- Action: Ask the user to review the changes closely.
- Do not commit or push.
- Provide a suggested Git commit message (e.g., "Cleanup: Resolve static analysis warnings in [Module]").
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 · 41 lines · 19 tokens per session scan A 7c318a431117
cleanup-code-inspections is a skill published in the GitHub repository flutter/flutter-intellij (2,019 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 19 tokens to every session and 390 once invoked, about $0.0001 per session on Opus 5.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
github-bugs-triage
Triages the open bug queue of the explyt/spring-plugin GitHub repository: fetches the oldest open issues of type Bug plus compatibility reports, refines titles, suggests labels, missing issue types and priorities with evidence, detects duplicates, and writes a structured triage table. Use when asked to triage…
java-code-review
Review Java code for bugs, duplicate code, correctness risks, maintainability improvements, and missing tests. By default review files modified in git; when the user explicitly names files, classes, packages, or a diff, review that scope instead. Generate a detailed review.md report with actionable comments and fixes.
adversarial-reviewer
Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…
gitnexus
A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…
codebase-review
Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.