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 skills/launch52-ai/flutter-template/flavorsnpx skills add launch52-ai/flutter-template --skill flavorsgit clone --depth 1 https://github.com/launch52-ai/flutter-templateWrote 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/skills/launch52-ai/flutter-template/flavors)<a href="https://agentmods.dev/skills/launch52-ai/flutter-template/flavors"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/flavors.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.00062 | $0.01486 |
| Opus 5 | $0.00031 | $0.00743 |
| Sonnet 5 | $0.00012 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00149 |
Grade A, and why
flavors 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flavors - Environment Configuration
Configure dev, staging, and production environments with separate configurations, bundle IDs, and app names.
When to Use This Skill
- Setting up multiple environments (dev, staging, prod)
- Separating API endpoints per environment
- Using different bundle IDs for each environment
- Configuring environment-specific Firebase/Supabase projects
- User asks "add flavors", "setup environments", "separate dev/prod"
When NOT to Use This Skill
- Single environment projects - Use
/initwith single.env - CI/CD setup - Use
/ci-cdafter flavors are configured - Basic Firebase setup - Use
/analyticsfirst, then add per-flavor config
Important: Migration from flutter_dotenv
This skill REPLACES flutter_dotenv runtime loading with compile-time variables.
If your project uses /init's approach (await dotenv.load()), running /flavors will:
- Remove
flutter_dotenvdependency - Replace
.envruntime loading with--dart-define-from-filebuild flags - Create
FlavorConfigclass usingString.fromEnvironment()
Why compile-time? Secrets are not bundled in the app binary - they're injected at build time.
Integration with /core
FlavorConfig handles:
- Flavor identification (
isDev,isProd,isStaging) - Per-flavor API URLs and service credentials
DebugConstants (from /core) handles:
- Debug/mock flags (
useMockAuth,useMockApi) - Logging and UI debug options
Keep feature flags in DebugConstants, flavor config in FlavorConfig.
Questions to Ask
- Flavor count: How many environments? (dev + prod, dev + staging + prod)
- Bundle ID pattern: How should bundle IDs differ? (suffix: .dev)
- App name pattern: How should app names differ? (suffix: " (Dev)")
- Firebase: Separate Firebase projects per flavor? (yes/no)
- Supabase: Separate Supabase projects per flavor? (yes/no)
Quick Reference
| Flavor | Bundle ID Suffix | App Name Suffix | Purpose |
|---|---|---|---|
| dev | .dev |
(Dev) |
Local development |
| staging | .staging |
(Staging) |
QA/testing |
| prod | (none) | (none) | Production release |
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- android-guide.md 8.9 KB
- checklist.md 4.7 KB
- firebase-guide.md 3.6 KB
- ios-guide.md 8.3 KB
- reference/flavor_config.dart 5.2 KB
- reference/main_flavored.dart 3.3 KB
- scripts/check.dart 20 KB
- templates/android/build_gradle_flavors.txt 748 B
- templates/env-files/env.dev.txt 1.5 KB
- templates/env-files/env.prod.txt 1.6 KB
- templates/env-files/env.staging.txt 1.5 KB
- templates/ios/Dev.xcconfig 364 B
- templates/ios/Prod.xcconfig 395 B
- templates/ios/Staging.xcconfig 382 B
- templates/vscode/launch.json 1.2 KB
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 · 178 lines · 62 tokens per session scan A fb00b8f56ede
flavors is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 62 tokens to every session and 1,486 once invoked, about $0.0003 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 skills, from other repositories
merge-seed
Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.
shadcn-ui-flutter
A comprehensive Flutter UI library inspired by shadcn/ui. Provides high-quality, customizable, and accessible components including Buttons, Cards, Forms, and more. Use this skill when building Flutter UIs, implementing design systems, or needing specific component usage examples.
at_client_skills-sdk
Use this skill when a developer is building a Dart or Flutter app that depends on atclient or atclientflutter from pub.dev, stores or shares data via the Atsign Protocol, needs onboarding (CRAM new-atsign, atKeys file, keychain, APKAM) or APKAM enrollment, or asks about AtCollection , CItem , Query , sub-collections…
update-store
ストア情報の更新自動化 — スクリーンショット撮影(シミュレーター × モック画面 × Marionette MCP)とメタデータテキスト更新。ストア更新、スクショ更新、App Store / Google Play のメタデータ更新、リリースノート作成の際に使用すること。.
mobile-automation
MCP (dart-mcp + Marionette) を使ったFlutterアプリのE2E自動化・UI検証ガイド。シミュレーターでのUI動作確認、モックプレビュー検証、Bridge経由のE2Eテスト、スクリーンショット撮影など、アプリの動作検証が必要なときに使う。「動作確認して」「UIを検証して」「E2Eテスト」「シミュレーターで確認」「モックで確認」と言われたときや、UI変更後の検証フェーズで使用すること。.
submit-store-review
App Store Connect・Google Playの現在の公開版をAPIで調べ、既存の最新安定ビルドとの差分から4言語のリリースノートを作成し、CLI/APIで審査へ提出・再提出する。新しいビルドを作るrelease-appとは分離し、「最新を審査提出して」「ストア審査へ提出して」「App Reviewに出して」「Google Playの審査を進めて」「却下対応して再提出して」と依頼されたときに使用する。.