flutter-template AGENTS.md

Repository instructions for a Flutter app template, a starting codebase for building mobile apps. They explain which project documents to read, where feature code belongs, and how the app's code generation and services are organized.

In plain words
What is it for?
Use them when adding screens or features, working with navigation, themes, localization, notifications, Firebase, or generated Flutter code in this repository.
Why use it?
They help an agent understand the template before changing it and reduce the risk of placing code incorrectly or assuming unfinished services are active.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/strvcom/flutter-template/agents-md
Clone the repo
git clone --depth 1 https://github.com/strvcom/flutter-template

Made for: Codex, OpenCode.

Per session 1,835 This file is loaded in full into every session.
When invoked 1,835 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01835 $0.01835
Opus 5 $0.00918 $0.00918
Sonnet 5 $0.00367 $0.00367
Haiku 4.5 $0.00184 $0.00184

Measured 2d ago against content hash 08548ef1e2dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flutter-template 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 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.

AGENTS.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Agent Guide

Use this file as the entrypoint for automated work in this repository.

Read Order

  1. docs/PROJECT_OVERVIEW.md for the repo map, startup flow, and feature inventory.
  2. docs/PROJECT_GUIDELINES.md for implementation conventions and workflow defaults.
  3. README.md for template setup, distribution, and platform-specific background.

Repo Summary

  • This is a Flutter template, not a fully productized app.
  • Core stack: flutter_riverpod, riverpod_annotation, freezed, json_serializable, auto_route, dio, Firebase services, and FVM-managed Flutter.
  • The app already includes example features, navigation, theming, codegen, localization, notifications, and release scaffolding.
  • Some integrations are intentionally scaffolded but not fully enabled yet. Check lib/app/setup/setup_app.dart before assuming a service is active.

Working Defaults

  • Keep new screen work inside lib/features/<feature>/.
  • Prefer the existing file pattern when a feature has state:
    • *_page.dart
    • *_page_content.dart
    • *_state.dart
    • *_event.dart
  • Keep page widgets thin. Put heavier UI in *_page_content.dart.
  • Prefer shared widgets and extensions from lib/common/ before introducing new app-specific primitives.
  • Keep network payload models in lib/common/data/dto/ and map them into entities from lib/common/data/entity/.
  • Use Riverpod providers and use cases instead of wiring IO directly in widgets.

Codegen And Commands

  • Run make gen after changing @riverpod, @freezed, @RoutePage, localization, or generated asset inputs.
  • Use make watch for continuous code generation when doing annotation-heavy work. This is a human-only command — agents must never run it (it spawns a persistent background watcher). Agents always use one-shot make gen.
  • Do not hand-edit generated files such as *.g.dart, *.freezed.dart, *.gr.dart, or files under lib/assets/.
  • Preferred validation commands:
    • fvm flutter analyze
    • fvm flutter test
    • make gen

Read the full file on GitHub · 112 lines

Changes

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.

  1. 2d ago First seen · 112 lines · 1,835 tokens per session scan A 08548ef1e2dd

Subscribe to this mod's changes

flutter-template AGENTS.md is an instructions file published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 1,835 tokens to every session, about $0.0092 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.