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 add-missing-unit-testgit 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/add-missing-unit-test)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/add-missing-unit-test"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/add-missing-unit-test/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/add-missing-unit-test"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/add-missing-unit-test.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.00036 | $0.00553 |
| Opus 5.5 | $0.00014 | $0.00221 |
| Sonnet 5.5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
add-missing-unit-test 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Add Missing Unit Test
You are tasked with adding a new unit test for a class that currently lacks one, or adding a new test case to an existing test file, to improve code coverage and reliability.
Objective
Add a new unit test for a class that currently lacks one, or add a new test case to an existing test file, to improve code coverage and reliability.
Workflow Instructions
1. Identify Target
- Choose a class in
src/that has complex logic but logic coverage is missing or incomplete.
2. Establish Baseline
- Run
./gradlew testClassesto compile all sources (production and test) and ensure the project is in a valid state. - Run
./gradlew verifyPluginto ensure no plugin verification issues exist. - Run
./gradlew test(or specific test if it exists) to establish current pass/fail status. - Run tests with Kover (
./gradlew koverHtmlReportor./gradlew koverXmlReport) to determine current coverage percentage for target class.
3. Implement Test
- Create a new test class (
[ClassName]Test) intestSrc/if it doesn't exist. - Add test cases to cover specific methods, edge cases, and branches.
- Ensure the test follows project testing conventions (naming, mocking, assertions).
4. Verify
- Run
./gradlew testClassesto ensure new test compiles. - Run new test (and related tests) to ensure it passes.
- Run
./gradlew verifyPluginto ensure no regressions in plugin verification. - Run Kover again to confirm coverage improvement.
5. Report & Review
- Summarize test added and coverage improvement.
- Test Location: Explicitly state where in the IDE user should go to test changed functionality (e.g., "Run the new test file
[TestFileName]"). - Action: Ask user to review new test closely. Validate that code being tested is actively used (e.g., check that it is not dead code/0 references).
- Do not commit or push.
- Provide a suggested Git commit message, explicitly including the Kover coverage improvement:
- Example Pattern:
Add unit tests for [Class Name]. Coverage verified using Kover. Coverage improvement: [Class Name]: ~[X]% line coverage ([Y] covered, [Z] uncovered).
- Example Pattern:
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 · 42 lines · 36 tokens per session scan A fa5cfcba9629
add-missing-unit-test is a skill published in the GitHub repository flutter/flutter-intellij (2,019 stars, last pushed today), licensed BSD-3-Clause. It adds 36 tokens to every session and 553 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
java-affected-tests
Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer runs the Java integration tests (they run only in the merge queue) and the JavaUIIT/search-it suites run only nightly, so this selects the unit tests and…
java-unit-test
A code-generation guide for Java unit tests in Spring Boot projects. Unit tests check one small piece of code in isolation; Spring Boot is a Java framework for building web applications and services.
verify-work
Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.
mockito
Use when generating mocks, stubbing methods, verifying interactions, capturing arguments, or choosing between mocks, fakes, and real objects (Mockito).
testing
Use when writing or reviewing Flutter/Dart tests (unit, widget, golden), fixing flaky tests, adding coverage, or choosing between unit and widget tests.
write-fixture
Write Java/Kotlin tests with Fixture Monkey — enumerate the cases a method can produce, pick the ones worth testing, and build each fixture pinning only the properties that force the expected outcome.