flavors

flavors is a skill for Claude Code, Codex from launch52-ai/flutter-template. It costs 62 tokens per session (1,486 once invoked), scanned A, original, MIT.

A setup tool for separate Flutter app environments such as development, staging, and production. Flutter is a framework for building apps, and each environment can use different settings such as API endpoints or app identifiers.

In plain words
What is it for?
Use it to configure Dart build variables, Android product flavors, iOS schemes, bundle IDs, app names, and environment-specific services.
Why use it?
It keeps testing and production configurations separate and replaces runtime .env loading with values supplied when the app is built.

Skill for Claude CodeCodex

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 skills/launch52-ai/flutter-template/flavors
Any agent
npx skills add launch52-ai/flutter-template --skill flavors
Clone the repo
git clone --depth 1 https://github.com/launch52-ai/flutter-template

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for flavors

README.md
[![agentmods](https://agentmods.dev/badge/skills/launch52-ai/flutter-template/flavors.svg)](https://agentmods.dev/skills/launch52-ai/flutter-template/flavors)
Your own site
<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>
Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,486 The whole file, excluding the scripts and references it only reads on demand.
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.00062 $0.01486
Opus 5 $0.00031 $0.00743
Sonnet 5 $0.00012 $0.00297
Haiku 4.5 $0.00006 $0.00149

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

Security

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.

.claude/skills/flavors/SKILL.md · 178 lines

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 /init with single .env
  • CI/CD setup - Use /ci-cd after flavors are configured
  • Basic Firebase setup - Use /analytics first, 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:

  1. Remove flutter_dotenv dependency
  2. Replace .env runtime loading with --dart-define-from-file build flags
  3. Create FlavorConfig class using String.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

  1. Flavor count: How many environments? (dev + prod, dev + staging + prod)
  2. Bundle ID pattern: How should bundle IDs differ? (suffix: .dev)
  3. App name pattern: How should app names differ? (suffix: " (Dev)")
  4. Firebase: Separate Firebase projects per flavor? (yes/no)
  5. 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

Read the full file on GitHub · 178 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. 4d ago First seen · 178 lines · 62 tokens per session scan A fb00b8f56ede

Subscribe to this mod's changes

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.

Related

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.

kriasoft/react-starter-kit · 49 tokens

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.

nank1ro/flutter-shadcn-ui · 58 tokens

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…

atsign-foundation/at_client_sdk · 232 tokens

update-store

ストア情報の更新自動化 — スクリーンショット撮影(シミュレーター × モック画面 × Marionette MCP)とメタデータテキスト更新。ストア更新、スクショ更新、App Store / Google Play のメタデータ更新、リリースノート作成の際に使用すること。.

K9i-0/ccpocket · 80 tokens

mobile-automation

MCP (dart-mcp + Marionette) を使ったFlutterアプリのE2E自動化・UI検証ガイド。シミュレーターでのUI動作確認、モックプレビュー検証、Bridge経由のE2Eテスト、スクリーンショット撮影など、アプリの動作検証が必要なときに使う。「動作確認して」「UIを検証して」「E2Eテスト」「シミュレーターで確認」「モックで確認」と言われたときや、UI変更後の検証フェーズで使用すること。.

K9i-0/ccpocket · 138 tokens

submit-store-review

App Store Connect・Google Playの現在の公開版をAPIで調べ、既存の最新安定ビルドとの差分から4言語のリリースノートを作成し、CLI/APIで審査へ提出・再提出する。新しいビルドを作るrelease-appとは分離し、「最新を審査提出して」「ストア審査へ提出して」「App Reviewに出して」「Google Playの審査を進めて」「却下対応して再提出して」と依頼されたときに使用する。.

K9i-0/ccpocket · 126 tokens