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/ofcskn/mobile-automation-plugin/submitting-app-releasenpx skills add ofcskn/mobile-automation-plugin --skill submitting-app-releasegit clone --depth 1 https://github.com/ofcskn/mobile-automation-pluginWrote 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/ofcskn/mobile-automation-plugin/submitting-app-release)<a href="https://agentmods.dev/skills/ofcskn/mobile-automation-plugin/submitting-app-release"><img src="https://agentmods.dev/badge/skills/ofcskn/mobile-automation-plugin/submitting-app-release.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.1 | $0.00072 | $0.00747 |
| Opus 5 | $0.00036 | $0.00374 |
| Sonnet 5 | $0.00014 | $0.00149 |
| Haiku 4.5 | $0.00007 | $0.00075 |
Grade A, and why
submitting-app-release 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Submitting App Release
Credential check — always run first
Before any submission step, load and run the credential check from:
skills/submitting-app-release/references/credentials-guide.md
Check all required vars, validate their format, and run eas whoami. If anything fails, stop and guide the user to fix it before running any build or submit command.
When to use
| Request | Action |
|---|---|
| "submit app" / "release" | Run checklist → submit both platforms |
| "submit iOS only" | Run checklist --platform ios → eas submit --platform ios |
| "submit Android only" | Run checklist --platform android → eas submit --platform android |
| "pre-flight check" | Run release-checklist.js only, no submission |
Release sequence
-
Run all 7 pre-flight gates:
node skills/submitting-app-release/scripts/release-checklist.js {appId} -
If all gates pass:
# iOS — phased release (7-day automatic rollout) eas submit --platform ios --profile production # Android — staged rollout (10% initial) eas submit --platform android --profile production -
Report submitted version and review status to user.
The 7 pre-flight gates
.msd/config/{appId}.config.jsonexists.msd/versions/{appId}/version.jsonis valid (semver + versionCode ≥ 1)- Metadata passes all character limit validation
- All translation keys present across all locales
- Designed screenshots exist for required device sizes
- EAS credentials configured (
eas whoamipasses, secrets set) - CHANGELOG.md includes the current version number
Rules
- Never auto-proceed past a failing gate. Stop and report to user.
- iOS staged release: enable phased release in App Store Connect after submission
- Android staged rollout: set rollout to 10% in Google Play Console, expand after 48h monitoring
EAS environment variables
| Variable | Purpose |
|---|---|
EXPO_TOKEN |
EAS authentication token (CI/CD) |
APP_STORE_CONNECT_API_KEY_ID |
App Store Connect API key ID |
APP_STORE_CONNECT_ISSUER_ID |
App Store Connect issuer ID |
APP_STORE_CONNECT_API_KEY_CONTENT |
App Store Connect API private key (base64) |
GOOGLE_SERVICES_JSON |
Google Play service account key (JSON string) |
What ships with it
5 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.
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.
- 5d ago First seen · 83 lines · 72 tokens per session scan A 52ade96af4dd
submitting-app-release is a skill published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 747 once invoked, about $0.0004 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
flutter-cherry-pick
How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter- . -candidate.0.
engine-whats-new
Generates the "what's new" release summary and diff file for changes in the Flutter engine (//engine/src/flutter) between two releases (e.g., 3.47 vs 3.44). When to use: - Only activate when explicitly asked by the user to generate what's new in the engine, diff Flutter engine releases, or produce an engine release…
find-release
A skill to find the lowest Dart and Flutter release containing a given commit. Use this skill whenever users ask about when a commit landed in Flutter or Dart releases, inquire about release versions for specific SHAs, or want to know if a commit is included in stable, beta, or dev channels for Flutter/Dart projects.
release-app
アプリのリリース（バージョンbump + CHANGELOG + タグ → GH Actions で自動ビルド・配布）。iOS / Android / macOS / Linux / Windows の任意の組み合わせでリリースできる。「リリース」「バージョン上げて」「リリースして」と言われたときに使う。.
shorebird-patch
Shorebird OTA パッチの作成・staging 配布（stable 昇格はユーザー実施）.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.