flutter-template CLAUDE.md

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.

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.

Security

Grade A, and why

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

CLAUDE.md · 118 lines

How it starts

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

/init                    # Initialize project, gather requirements, flutter create
/core                    # Generate core infrastructure (theme, services, router)
/auth                    # Generate authentication feature
/social-login            # Add social login (if needed)
/phone-auth              # Add phone auth (if needed)
/local-auth              # Add biometric unlock (if needed)
/push-notifications      # Add push notifications (if needed)
/deep-linking            # Add deep linking (if needed)
/network-connectivity    # Add offline banner (if needed)
/offline                 # Add offline-first architecture (if needed)
/force-update            # Add force update prompts (if needed)
/flavors                 # Add dev/staging/prod environments (if needed)
/analytics               # Add analytics & crash reporting
/in-app-purchases        # Add subscriptions/purchases (if needed)
/feature-init dashboard  # Initialize dashboard scaffold
/feature-init settings   # Initialize settings scaffold
/account-deletion        # Add account deletion (App Store & Play Store required)
/i18n                    # Add localization
/release                 # When ready for app stores

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.

Related

Other instructions, from other repositories