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-dependenciesnpx skills add flutter/flutter-intellij --skill audit-dependenciesgit 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-dependencies)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/audit-dependencies"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/audit-dependencies.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 | $0.00018 | $0.00412 |
| Opus 5 | $0.00009 | $0.00206 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
audit-dependencies 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 4d 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: Dependency & Library Audit
You are tasked with optimizing plugin size and security by removing unused dependencies and updating outdated libraries.
Objective
Optimize plugin size and security by removing unused dependencies and updating outdated libraries.
Workflow Instructions
1. Baseline
- Run
./gradlew testand./gradlew verifyPluginto ensure the project is stable.
2. Audit build.gradle
- Review
dependencies {}block. Identify libraries that might no longer be used.
3. Check plugin.xml
- Ensure all
<depends>tags match actual API usage.
4. Update Versions
- Check for newer stable versions of third-party libraries.
5. Remove Unused
- Delete any local
.jarfiles inlib/that are not referenced or can be replaced by Maven coordinates.
6. Verify
- Run
./gradlew buildPluginand check the distribution size. Ensure the plugin still loads and functions correctly. - Run
./gradlew testClasses,./gradlew test, and./gradlew verifyPluginto ensure no checking or runtime issues were introduced. - 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 dependencies removed or updated.
- 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
build.gradlechanges closely. - Do not commit or push.
- Provide a suggested Git commit message (e.g., "Cleanup: Remove unused dependency [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.
- 4d ago First seen · 41 lines · 18 tokens per session scan A 9c43dcda3f23
audit-dependencies is a skill published in the GitHub repository flutter/flutter-intellij (2,013 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 18 tokens to every session and 412 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) のテスト実行・型チェック・テスト記述ガイド.
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.
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-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.
jaspr-fundamentals
Use when working in a Jaspr project, on Jaspr components, or other Jaspr-related tasks. Contains fundamentals of writing Jaspr components and using HTML components.