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/ofershap/flutter-best-practices/auditgit clone --depth 1 https://github.com/ofershap/flutter-best-practicesWhat 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.00012 | $0.00195 |
| Opus 5 | $0.00006 | $0.00097 |
| Sonnet 5 | $0.00002 | $0.00039 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
audit 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 yesterday.
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
Scan the current project for Flutter anti-patterns and best practice violations.
Check for:
- Navigator 1.0 (push/pop) instead of GoRouter
- Pre-Dart 3 patterns (if/else chains vs sealed classes, Map vs records)
- StatefulWidget with setState for shared state instead of Riverpod
- Missing const constructors where applicable
- Hardcoded colors/sizes instead of Theme.of(context)
- Nested scrollable widgets (ListView in Column)
- Raw String/int IDs instead of extension types
- Using dynamic instead of proper types
- Context used after async gap (mounted check)
For each issue found:
- Show the file and line
- Explain what's wrong
- Show the correct pattern
- Rate severity: critical / warning / info
Use the flutter-best-practices skill for reference on current best practices.
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.
- yesterday First seen · 28 lines · 12 tokens per session scan A ddc8ebf1fcb2
audit is a command published in the GitHub repository ofershap/flutter-best-practices (1 stars, last pushed 6mo ago), licensed MIT. It adds 12 tokens to every session and 195 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-31.
Other commands, from other repositories
implement-plan
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.
use-faq-diagram
Please analyse using ecs DESIGN and DX FAQ (and the FAQ files in plugins) and ecsarchitecturediagram for correct understanding of reusable parts.
update-diagram
please update .cursor/rules/architecturediagram.mdc to support all our current relationships and Key Data Flow.
cleanup
clean up deprecated code, logic that makes no sense or is not needed anymore.
apply-to-plan
please apply to the plan what you find useful and relevant.
inconsistences
TODOs, errors, incosistencies, potential code and typesafety violations in.