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 audit-accessibilitygit 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/audit-accessibility)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/audit-accessibility"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/audit-accessibility/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/audit-accessibility"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/audit-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 18 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00024 | $0.00458 |
| Opus 5.5 | $0.00010 | $0.00183 |
| Sonnet 5.5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
audit-accessibility 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: Accessibility (A11y) Audit
You are tasked with ensuring the plugin's custom UI components are accessible to users with screen readers and other assistive technologies.
Objective
Ensure the plugin's custom UI components are accessible to users with screen readers and other assistive technologies.
Workflow Instructions
1. Baseline
- Run
./gradlew testClassesto ensure project compilation. - Run
./gradlew testto ensure the project is stable. - Run
./gradlew verifyPluginto ensure no verification issues.
2. Identify Custom UI
- List all custom
JPanel,JComponent, orDialogclasses in the codebase.
3. Check Properties
- Verify that every interactive component has:
getAccessibleContext().setAccessibleName(...)getAccessibleContext().setAccessibleDescription(...)
4. Focus Management
- Ensure custom components handle focus traversal correctly (Tab/Shift+Tab).
5. Color Contrast
- If custom colors are used, verify they meet WCAG contrast guidelines (especially for dark themes).
6. Verify
- Run
./gradlew testClassesand./gradlew testto ensure no regressions. - Run
./gradlew verifyPluginto ensure strict compliance. - Use the "Accessibility Inspector" (if available in the SDK) or a screen reader to navigate the UI.
- Suggest manual test steps: Check the code changes made and write test steps for a user to execute that will trigger the code paths that have changed. If needed, add logging statements to verify that the code paths have successfully run.
7. Report & Review
- Summarize the accessibility improvements in the form of a git commit message.
- 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 UI changes closely.
- Do not commit or push.
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 · 45 lines · 24 tokens per session scan A ed4f302c06b0
audit-accessibility is a skill published in the GitHub repository flutter/flutter-intellij (2,019 stars, last pushed today), licensed BSD-3-Clause. It adds 24 tokens to every session and 458 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
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.
eddi-screens
How an EDDI Manager page is actually built — the app shell, the list-page pattern, detail pages, the config-editor chrome, wizards, and loading/empty/error states. Load before creating or restructuring a page.
eddi-ui
EDDI Manager's UI vocabulary — the existing primitives and shared components, their variant props, the brand tokens, and the styling rules. Load before writing or editing any component that renders.
common-architecture-diagramming
Draws architecture diagrams as editable draw.io files with a fixed house style, C4 levels, evidence-tagged shapes, and optional multi-view identity checks. Use when producing a system context, container, component, deployment, data flow, sequence, state, or ERD, or redrawing an ASCII or Mermaid one.
system-design-diagramming
Draw system diagrams in the Archify visual language: a typed JSON spec rendered as dark-canvas SVG with numbered lanes, semantic node colors, masked edge labels, and a legend. Covers architecture, workflow, sequence, dataflow, and lifecycle views. Use for any design-session diagram.
common-stitch-design
Drive Google Stitch over MCP safely - read screens, write and lint DESIGN.md, create design systems, and fix designs through variants instead of overwriting. Use when reviewing, editing, or generating Stitch screens or DESIGN.md files.