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 instructions/evanca/flutter-ai-rules/agents-mdgit clone --depth 1 https://github.com/evanca/flutter-ai-rulesWhat 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.00156 | $0.00156 |
| Opus 5 | $0.00078 | $0.00078 |
| Sonnet 5 | $0.00031 | $0.00031 |
| Haiku 4.5 | $0.00016 | $0.00016 |
Grade A, and why
flutter-ai-rules AGENTS.md 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 3d 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
Global Agent Rules
- Be concise. The owner works on several apps in parallel and has limited time to read your outputs; don't use a full paragraph when a single short sentence will do.
- Keep files small and modular; split large files into reusable parts.
- After each task, run
afplay /System/Library/Sounds/Glass.aiff. - After each step, suggest a short commit title:
Implement dashboardfor features;Fix: Problemfor fixes. Use no other prefixes. - After deploying Flutter to Chrome, press
r; restart it ifpubspec.yamlor assets changed. - Write every skill’s YAML
descriptionon one line starting withUse when; include only trigger conditions.
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.
- 3d ago First seen · 9 lines · 156 tokens per session scan A 4e9699364171
flutter-ai-rules AGENTS.md is an instructions file published in the GitHub repository evanca/flutter-ai-rules (622 stars, last pushed 5d ago), licensed MIT. It adds 156 tokens to every session, about $0.0008 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 instructions, from other repositories
masterfabric_core AGENTS.md
AGENTS.md instructions for gurkanfikretgunak/masterfabric_core: This project's development guide has been moved to .cursor/AGENTS.md.
wind docs.instructions.md
Instructions for fluttersdk/wind, covering documentation conventions (doc/), file shape (every doc file), wfoo, basic usage and props.
wind copilot-instructions.md
Instructions for fluttersdk/wind, covering wind ui, definition of done, post-change sync (five surfaces, every code change), commands and coverage policy (binding).
dart-expert-skills skills.instructions.md
Instructions for Poorgramer-Zack/dart-expert-skills, covering agent skill authoring best practices, yaml frontmatter requirements, conciseness rules, content structure and progressive disclosure.
codewalk AGENTS.md
AGENTS.md instructions for verseles/codewalk, covering codewalk project rules, tracking, project context, required context and documentation.
firebase-cloud-messenger AGENTS.md
Instructions for az-coder-123/firebase-cloud-messenger, covering agents.md, development guidelines, 1. code clarity and maintainability, 2. state management and 3. library usage.