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/update-faqgit clone --depth 1 https://github.com/Arenukvern/mcp_flutterWrote 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/commands/arenukvern/mcp_flutter/update-faq)<a href="https://agentmods.dev/commands/arenukvern/mcp_flutter/update-faq"><img src="https://agentmods.dev/badge/commands/arenukvern/mcp_flutter/update-faq.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.00000 | $0.00285 |
| Opus 5 | $0.00000 | $0.00143 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
update-faq 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
could you please update DESIGN_FAQ & DX_FAQ based on the changes we are trying to achieve.
the goal is not to write many lines of docs, but have concise document with key design decisions made in projects - so we could easily explain why we are done something, instead of how
idea is:
- DESIGN_FAQ - Focus on Why (design decisions): for maintaining the ECS - to concentrate more on why instead of how. Make it shortest form of FAQ understandable for AI Agent.
For example: Q: Why we cannot use Entity.index and should get its location? A: Because etc..
Keep concise & short: 2-3 sentences, include key trade-offs and rationale.
- DX_FAQ - Focus on How (usage): Developer Experience API is how we can use ecs from developer perspective. Use Memory Palace Format - spatial organization with mental "locations" (🏠 World Hub, 🏭 Entity Factory, etc.) containing embedded code patterns for maximum AI agent memory retention.
Rules
-
Always check against codebase and suggest best patterns and practices.
-
Achieve changes: new content + making existing docs more concise. Short & Smart.
-
Optimize for AI agent understanding using spatial memory techniques.
-
No duplication between the two documents
-
For DX_FAQ: Structure as Memory Palace with locations containing code patterns, decision matrices, and memory hooks.
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 · 28 lines · 0 tokens per session scan A 2d61ddc3deac
update-faq is a command published in the GitHub repository Arenukvern/mcp_flutter (373 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 285 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のデュアルレビューで多角的に検証。.
inspect-widget
Command "inspect-widget" from K9i-0/flutter_claude_sandbox, covering inspect selected widget, 手順, 使用するdart mcpツール and 注意事項.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.