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/nylo-core/claude-code/flutter-releasenpx skills add nylo-core/claude-code --skill flutter-releasegit clone --depth 1 https://github.com/nylo-core/claude-codeWhat 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.00045 | $0.04015 |
| Opus 5 | $0.00023 | $0.02008 |
| Sonnet 5 | $0.00009 | $0.00803 |
| Haiku 4.5 | $0.00005 | $0.00402 |
Grade C, and why
flutter-release scanned grade C with 2 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/install/main/install.sh -sSf | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl --proto '=https' --tlsv1.2 https://raw.githubusercontent.com/shorebirdtech/install/main/install.sh -sSf | bash How it starts
The opening of the file, as written. The whole thing — 466 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flutter Release and Store Submission
Overview
Releasing a Flutter app involves building platform-specific artifacts (AAB/APK for Android, IPA for iOS), then submitting them to Google Play Console or App Store Connect. Each store has specific requirements for listing metadata, screenshots, ratings, and compliance.
When to Use
- User wants to build a release version of the app
- User is preparing for first submission to App Store or Google Play
- User needs to know what build commands to run
- User wants to understand store listing requirements
- User is submitting an update to an existing app
- NOT for debug builds or development testing (use
flutter run)
Quick Reference: Build Commands
| Artifact | Command | Output Location |
|---|---|---|
| Android APK | flutter build apk |
build/app/outputs/flutter-apk/app-release.apk |
| Android APK (split per ABI) | flutter build apk --split-per-abi |
build/app/outputs/flutter-apk/app-*-release.apk |
| Android App Bundle | flutter build appbundle |
build/app/outputs/bundle/release/app-release.aab |
| iOS IPA | flutter build ipa |
build/ios/ipa/*.ipa |
| iOS (no signing) | flutter build ios --no-codesign |
build/ios/iphoneos/Runner.app |
Pre-Release Checklist
Before building for release, verify:
- Version and build number incremented in
pubspec.yaml - Code signing configured (see flutter-signing skill)
- App icon set (see flutter-app-icons skill)
- Splash screen configured (see flutter-app-icons skill)
- App name and bundle ID finalized (see flutter-app-config skill)
- Debug-only code removed (print statements, debug banners)
-
flutter analyzepasses with no errors - All tests pass:
flutter test - Permissions configured with proper usage descriptions (see flutter-permissions skill)
- ProGuard/R8 rules configured if using code shrinking (Android)
-
minSdkVersionand deployment target set appropriately
Building for Android
Android App Bundle (AAB) — Recommended for Google Play
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.
- 2d ago First seen · 466 lines · 45 tokens per session scan C 6951e672d588
flutter-release is a skill published in the GitHub repository nylo-core/claude-code (4 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 4,015 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
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…
flutter-pre-caching
Use when preloading fonts, asset/network images, Lottie/Rive animations, local JSON/config, warming initial API data, or optimizing Flutter Web startup.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
bloc
Use when creating a Cubit or Bloc, modeling state with sealed classes or status enums, wiring BlocBuilder/BlocListener/BlocProvider, writing bloc tests, or choosing between Cubit and Bloc.
firebase-auth
Use when setting up auth, managing auth state, implementing email/password or social sign-in, handling auth errors, or managing users.
dart-3-updates
Use when writing switch statements, refactoring if-else chains, creating data classes, choosing records vs classes, destructuring values, or modernizing pre-Dart-3 code.