expo-setup

expo-setup is a skill for Claude Code from berkcangumusisik/claude-code-practices. It costs 20 tokens per session (320 once invoked), scanned A, original, MIT.

A setup workflow for Expo applications, including EAS Build, over-the-air updates, and app configuration. Expo is a framework for building mobile apps with JavaScript or TypeScript, while EAS provides Expo's build and update services.

In plain words
What is it for?
It helps configure app identifiers, deep links, icons, and splash screens; create EAS build profiles; set up over-the-air updates; and generate GitHub Actions workflows for preview and production builds.
Why use it?
It checks the current mobile-app configuration and prepares the files, build profiles, update settings, and automation needed for development, preview, and production builds.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit It helps configure app identifiers, deep links, icons, and splash screens; create EAS build profiles; set up over-the-air updates; and generate GitHub Actions workflows for preview and production builds.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/berkcangumusisik/claude-code-practices/expo-setup
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 berkcangumusisik/claude-code-practices --skill expo-setup
Clone the repo
git clone --depth 1 https://github.com/berkcangumusisik/claude-code-practices

Made for: Claude Code.

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-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/expo-setup.svg)](https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/expo-setup)
Your own site
<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/expo-setup"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/expo-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 320 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.00320
Opus 5 $0.00010 $0.00160
Sonnet 5 $0.00004 $0.00064
Haiku 4.5 $0.00002 $0.00032

Measured 7d ago against content hash 57bc768770ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

expo-setup 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 7d 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.

skills/expo-setup/SKILL.md · 54 lines

What it actually says

Expo / EAS Setup

Platform: $1 (ios | android | all - default: all)

  1. Check current state:
cat app.json 2>/dev/null
cat eas.json 2>/dev/null
npx expo-env-info 2>/dev/null | head -10
  1. Configure app.json:

    • expo.name, expo.slug set correctly?
    • iOS: bundleIdentifier set?
    • Android: package set?
    • scheme for deep links?
    • icon and splash configured?
  2. Generate eas.json with 3 profiles:

{
  "build": {
    "development": {
      "developmentClient": true,
      "distribution": "internal"
    },
    "preview": {
      "distribution": "internal",
      "channel": "preview"
    },
    "production": {
      "autoIncrement": true
    }
  }
}
  1. Set up OTA updates config (expo-updates).

  2. Generate GitHub Actions workflow for:

    • PR → build preview
    • Main push → production build
  3. Document secrets needed in GitHub/EAS secrets.

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. 7d ago First seen · 54 lines · 20 tokens per session scan A 57bc768770ba

Subscribe to this mod's changes

expo-setup is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (10 stars, last pushed 4mo ago), licensed MIT. It adds 20 tokens to every session and 320 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-31.