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 load-repo-contextgit 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/load-repo-context)<a href="https://agentmods.dev/skills/flutter/flutter-intellij/load-repo-context"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/load-repo-context/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/load-repo-context"><img src="https://agentmods.dev/badge/skills/flutter/flutter-intellij/load-repo-context.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00018 | $0.00133 |
| Opus 5.5 | $0.00007 | $0.00053 |
| Sonnet 5.5 | $0.00004 | $0.00027 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
load-repo-context 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 24d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- load-repo-context — 100% identical, 0 lines differ
What it actually says
Load Repository Context
Primes understanding of repository architecture by navigating hierarchical ABOUT.md manifests before inspecting or modifying source code.
Instructions
- Read the root
./ABOUT.mdto map top-level subsystems. - Identify which subsystem subdirectories are relevant to the active user prompt.
- Traverse and read only the targeted child
ABOUT.mdfiles. Do not load raw source code yet. - Present a 3-5 bullet point architectural summary of the targeted components to establish the "Elephant" context.
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.
- 24d ago First seen · 16 lines · 18 tokens per session scan A d09169a49c87
load-repo-context is a skill published in the GitHub repository flutter/flutter-intellij (2,018 stars, last pushed today), licensed BSD-3-Clause. It adds 18 tokens to every session and 133 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-09-22.
Other skills, from other repositories
cosmos-run-integration-tests
Run azure-cosmos integration/customer-workflow tests locally, closely following the CI pipeline (build+install, then failsafe verify with a test profile) using one consistent JDK for both steps. USE WHEN: asked to run cosmos integration tests, customer-workflow tests (fi-customer-workflows / fi-sm-customer-workflows)…
tool-assistant
Tool-calling assistant with backend functions for time, city time, weather, and temperature conversion, plus cost metering and approval workflows. Use when a question needs real-time data via tool calls.
self-improve
Use when running ChaosEngine Learning Session self-improve. Harness lessons are GitHub issues only. Product lessons may queue after delivery or on request.
Pair Programming
Collaboratively design, implement, review, and refine software features with a human developer using an iterative pair programming workflow. Prioritize understanding, explicit approval, small reviewable changes, and synchronized specifications.
042-planning-openspec
Use when creating or updating OpenSpec artifacts from an issue, plan, approved design, ADRs, existing OpenSpec, or a valid combination. The workflow assesses reviewable scope, records source authority and derivation, handles conflicts, and prevents silent synchronization. Triggers include Create OpenSpec from an…
043-planning-github-issues
Use when you need GitHub CLI (gh) installation/authentication guidance and an operator-only GitHub issue inventory workflow. The agent does not ingest GitHub issue, milestone, body, comment, title, label, or summary text; requirements analysis must use repository-owned planning artifacts, with issue numbers only for…