What is submitting-app-release?

A release workflow for sending a mobile app to Apple’s App Store and Google Play after required checks pass.

Use it to run release checks and submit an iOS app, an Android app, or both through EAS CLI.

It catches missing credentials or failed pre-release checks before an app is submitted for store review.

submitting-app-release — Skill for Claude Code by ofcskn

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.

Any agent

npx skills add ofcskn/mobile-automation-plugin --skill submitting-app-release

Clone the repo

git clone --depth 1 https://github.com/ofcskn/mobile-automation-plugin

Made for: Claude Code.

Or install automobileapp, the plugin that ships this one along with the rest of its 11 skills, 17 commands.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ofcskn/mobile-automation-plugin/submitting-app-release/github.svg)](https://agentmods.dev/skills/ofcskn/mobile-automation-plugin/submitting-app-release)

Your own site

<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 747 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00072	$0.00747
Opus 5.5	$0.00029	$0.00299
Sonnet 5.5	$0.00014	$0.00149
Haiku 4.5	$0.00007	$0.00075

Measured 2mo ago against content hash 52ade96af4dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo ago.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/generate-release-summary.js, scripts/release-checklist.js), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/submitting-app-release/SKILL.md · 83 lines

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.json exists
.msd/versions/{appId}/version.json is 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 whoami passes, 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)

Read the full file on GitHub · 83 lines

Files

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.

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.

2mo ago First seen · 83 lines · 72 tokens per session scan A 52ade96af4dd

Subscribe to this mod's changes

submitting-app-release is a skill published in the GitHub repository ofcskn/mobile-automation-plugin (2 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 747 once invoked, about $0.0003 per session on Opus 5.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.

Claude Code Git and workflow Mobile Releases android app-store automation claude-plugin expo

submitting-app-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
submitting-app-releaseofcskn/mobile-automation-plugin	Skill	2	4mo ago	MIT	A	72	Claude Code
manage-prswataru-maeda/react-native-boilerplate	Skill	524	6d ago	MIT	A	53	Claude Code, Codex
release-new-versionniki914/zafiro	Skill	340	4d ago	MIT	A	54	Claude Code, Codex
flame-harness-submittjdrhs90/flutter-flame-harness	Skill	61	10d ago	MIT	A	38	Claude Code
rn-harness-submittjdrhs90/rn-launch-harness	Skill	7	10d ago	MIT	A	35	Claude Code
gplay-release-flowPollyGlot/google-play-cli-skills	Skill	5	2d ago	MIT	A	74	Claude Code, Codex
eas-releaseAnilBurcu/claude-code-react-native	Skill	3	today	MIT	A	40	Claude Code