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 commands/arenukvern/mcp_flutter/implement-plangit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWhat 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.00000 | $0.00048 |
| Opus 5 | $0.00000 | $0.00024 |
| Sonnet 5 | $0.00000 | $0.00010 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
implement-plan 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 2d 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
Implement the plan as specified, it is attached for your reference. Do NOT edit the plan file itself. Create todos for the plan as you work, starting with the first one. Don't stop until you have completed all the to-dos.
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.
- 2d ago First seen · 3 lines · 0 tokens per session scan A 62671ec6afa4
implement-plan is a command published in the GitHub repository Arenukvern/mcp_flutter (372 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 48 tokens. 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 commands, from other repositories
building-flutter-apps-skill-ac1294fc
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
audit
Audit the current codebase for Flutter best practice violations.
agent-review
コード変更をセルフレビューする。Gemini CLI + Claude subagentのデュアルレビューで多角的に検証。.
implement-next
IMPORTANT: This is an EXECUTION command. Immediately start implementing without waiting for confirmation.
/opsx-ff
Create a change and generate all artifacts needed for implementation in one go.
colorize
Apply ColorScheme.fromSeed + semantic tokens throughout. Generates matching dark theme.