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/strvcom/flutter-template/release-buildsnpx skills add strvcom/flutter-template --skill release-buildsgit clone --depth 1 https://github.com/strvcom/flutter-templateWhat 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.00050 | $0.01088 |
| Opus 5 | $0.00025 | $0.00544 |
| Sonnet 5 | $0.00010 | $0.00218 |
| Haiku 4.5 | $0.00005 | $0.00109 |
Grade A, and why
release-builds 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.
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.
Flutter Template Release Builds
Use this skill only after the release PR has been merged.
Read First
AGENTS.mddocs/PROJECT_GUIDELINES.mdREADME.mdpubspec.yamlmakefile.github/workflows/.agents/skills/release-builds/scripts/archive_ios_ipa.sh
Goal
This skill is for the post-merge release-build phase.
It covers:
- Android release triggering by tags
- iOS IPA generation
- archiving IPA files outside the cleaned build folder for Transporter upload
- archiving Flutter obfuscation symbols from
build/app/outputs/symbolsfor Crashlytics Dart stack-trace deobfuscation
Android Release Flow
Android releases are triggered by tags after the release branch work is merged.
Current workflow tag patterns:
- develop Firebase distribution:
v<version>-develop - staging Firebase distribution:
v<version>-staging - production Firebase distribution:
v<version>-production - Play Store production:
v<version>-release
Before tagging:
- Confirm the merged commit and intended channel.
- Confirm the tag pattern matches the target workflow.
- Create the tag on the correct merged commit.
- Push the tag and monitor the corresponding GitHub Action.
iOS Release Flow
iOS release builds are manual and should be done one flavor at a time.
Why:
- each make target runs
make clean - each build clears the
build/directory - IPA files and Flutter obfuscation symbols must be copied out of
build/before the next build if you want to keep all generated artifacts
iOS Build Commands
- develop:
make generateIosDevelopIpa
- staging:
make generateIosStagingIpa
- production:
make generateIosProductionIpa
iOS Artifact Archival Workflow
Immediately after each IPA build, archive the IPA out of build/ios/ipa/ and Flutter obfuscation symbols out of build/app/outputs/symbols before starting the next build.
Use:
.agents/skills/release-builds/scripts/archive_ios_ipa.sh <flavor>
Examples:
.agents/skills/release-builds/scripts/archive_ios_ipa.sh develop.agents/skills/release-builds/scripts/archive_ios_ipa.sh staging.agents/skills/release-builds/scripts/archive_ios_ipa.sh production
What ships with it
1 file 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.
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 · 118 lines · 50 tokens per session scan A dcfd07789629
release-builds is a skill published in the GitHub repository strvcom/flutter-template (24 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 1,088 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-30.
Other skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
app_remix
Create a new Rome app from an App Store source, already installed or identified by a pinned Store version. Copy installed code locally or download and extract a Store bundle without installing the source. Never edit or overwrite an existing source app.