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 agentmods add skills/flutter/flutter-intellij/audit-accessibilitynpx skills add flutter/flutter-intellij --skill audit-accessibilitygit clone --depth 1 https://github.com/flutter/flutter-intellijWhat 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 | $0.00024 | $0.00458 |
| Opus 5 | $0.00012 | $0.00229 |
| Sonnet 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 3d 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.
- 3d 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,013 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 24 tokens to every session and 458 once invoked, about $0.0001 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
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.
test-bridge
Bridge Server (TypeScript) のテスト実行・型チェック・テスト記述ガイド.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
firebase-ai
Use when setting up firebaseai, generating text/chat with Gemini, streaming AI output, building multimodal prompts, or handling AI errors.
firebase-cloud-functions
Use when calling callable functions (httpsCallable), passing data to server-side logic, handling function errors/timeouts, configuring regions, or testing with the Emulator Suite.
common-feedback-reporter
Pre-write audit for skill violations: checks planned code against loaded skill anti-patterns before any file write. Use when writing Flutter/Dart/TS code or editing SKILL.md files with active project skills. Load as composite; on auto-fixed violation, also load +common/common-learning-log.