expo-deployment

expo-deployment is a skill for Claude Code, Codex from zai-org/Synapse. It costs 24 tokens per session (927 once invoked), scanned A, original, Apache-2.0.

Instructions for releasing Expo apps to the iOS App Store, Google Play, and the web using EAS, Expo’s hosted build and deployment service. It also covers deploying API routes and setting up automated workflows.

In plain words
What is it for?
Use it to create iOS and Android production builds, submit them to their app stores, publish web versions, prepare TestFlight betas, and configure continuous deployment.
Why use it?
It collects the build, submission, beta-testing, store-metadata, and automation steps needed to move an Expo app from development to distribution.

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/zai-org/synapse/expo-deployment
Any agent
npx skills add zai-org/Synapse --skill expo-deployment
Clone the repo
git clone --depth 1 https://github.com/zai-org/Synapse

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 expo-deployment

README.md
[![agentmods](https://agentmods.dev/badge/skills/zai-org/synapse/expo-deployment.svg)](https://agentmods.dev/skills/zai-org/synapse/expo-deployment)
Your own site
<a href="https://agentmods.dev/skills/zai-org/synapse/expo-deployment"><img src="https://agentmods.dev/badge/skills/zai-org/synapse/expo-deployment.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 927 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.00024 $0.00927
Opus 5 $0.00012 $0.00464
Sonnet 5 $0.00005 $0.00185
Haiku 4.5 $0.00002 $0.00093

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

Security

Grade A, and why

expo-deployment 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.agents/skills/expo-deployment/SKILL.md · 191 lines

How it starts

The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Deployment

This skill covers deploying Expo applications across all platforms using EAS (Expo Application Services).

References

Consult these resources as needed:

  • ./references/workflows.md -- CI/CD workflows for automated deployments and PR previews
  • ./references/testflight.md -- Submitting iOS builds to TestFlight for beta testing
  • ./references/app-store-metadata.md -- Managing App Store metadata and ASO optimization
  • ./references/play-store.md -- Submitting Android builds to Google Play Store
  • ./references/ios-app-store.md -- iOS App Store submission and review process

Quick Start

Install EAS CLI

npm install -g eas-cli
eas login

Initialize EAS

npx eas-cli@latest init

This creates eas.json with build profiles.

Build Commands

Production Builds

# iOS App Store build
npx eas-cli@latest build -p ios --profile production

# Android Play Store build
npx eas-cli@latest build -p android --profile production

# Both platforms
npx eas-cli@latest build --profile production

Submit to Stores

# iOS: Build and submit to App Store Connect
npx eas-cli@latest build -p ios --profile production --submit

# Android: Build and submit to Play Store
npx eas-cli@latest build -p android --profile production --submit

# Shortcut for iOS TestFlight
npx testflight

Web Deployment

Deploy web apps using EAS Hosting:

# Deploy to production
npx expo export -p web
npx eas-cli@latest deploy --prod

# Deploy PR preview
npx eas-cli@latest deploy

EAS Configuration

Standard eas.json for production deployments:

{
  "cli": {
    "version": ">= 16.0.1",
    "appVersionSource": "remote"
  },
  "build": {
    "production": {
      "autoIncrement": true,
      "ios": {
        "resourceClass": "m-medium"
      }
    },
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    }
  },
  "submit": {
    "production": {
      "ios": {
        "appleId": "[email protected]",
        "ascAppId": "1234567890"
      },
      "android": {
        "serviceAccountKeyPath": "./google-service-account.json",
        "track": "internal"
      }
    }
  }
}

Read the full file on GitHub · 191 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.

  1. 4d ago First seen · 191 lines · 24 tokens per session scan A 81b700b0cfe1

Subscribe to this mod's changes

expo-deployment is a skill published in the GitHub repository zai-org/Synapse (454 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 927 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

agent-browser

Browser automation via Chrome/Chromium CDP — open, snapshot, click, screenshot. For testing web apps, mobile layouts, and automated interactions without Playwright/Puppeteer.

x-cmd/x-cmd · 39 tokens

generate-appclaw-flow

Generate YAML flow files for AppClaw mobile automation. Handles structured steps, natural language steps, phased flows (setup/steps/assertions), variable and secret interpolation via .appclaw/env/, and validation. Trigger when the user wants to create, edit, or fix a YAML flow file for AppClaw.

appclawhq/AppClaw · 69 tokens

use-appclaw-agent-cli

Use the appclaw-agent CLI to directly open, inspect, and interact with a mobile app via terminal commands — without writing a YAML flow. Trigger this skill when the user asks to open an app, tap or fill a UI element, check visibility, or perform any one-off device interaction that does not require a reusable flow file.

appclawhq/AppClaw · 74 tokens

deploy-after-ci

BoardGame 生产更新最短路径。用于更新部署、发生产、更新线上;默认 CI 构建后直传镜像到服务器并 update-local + Android stable OTA,提 CI 时先查 Actions/Docker。.

zhuanggenhua/BoardGame · 52 tokens

promote-to-production

Promote an already-built AAB from the Play internal track to one or more downstream tracks — closed testing (alpha), open testing (beta), and/or production — by dispatching the "Promote to Production" GitHub Action, then guiding the gated approval. Use when the user wants to ship the latest internal build to…

kikin81/nubecita · 88 tokens

eas-mobile-deployment

Explains how EAS Build and Submit work together for App Store and Google Play deployment. Use when configuring eas.json, troubleshooting mobile builds/submissions, or understanding version management, submit profiles, and the build-then-submit pipeline.

Ampli-Group/agentic-mobile-blueprint · 52 tokens