configuring-expo

configuring-expo is a skill for Claude Code from rahulkeerthi/expo-toolkit. It costs 36 tokens per session (2,879 once invoked), scanned C, original, MIT.

A configuration guide for Expo, a framework for building mobile apps with JavaScript or TypeScript. It covers app.config.js, environment variables, and settings that vary between development, preview, and production builds.

In plain words
What is it for?
Use it to set up dynamic Expo configuration, assign environment-specific app identifiers, and troubleshoot Expo project settings.
Why use it?
It helps avoid configuration errors when the same app needs different settings or separate installable versions for different environments.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the expo-toolkit plugin — 6 skills, 7 commands, 5 agents shipped together

Good fit Use it to set up dynamic Expo configuration, assign environment-specific app identifiers, and troubleshoot Expo project settings.

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

Made for: Claude Code.

Or install expo-toolkit, the plugin that ships this one along with the rest of its 6 skills, 7 commands, 5 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/rahulkeerthi/expo-toolkit/configuring-expo/github.svg)](https://agentmods.dev/skills/rahulkeerthi/expo-toolkit/configuring-expo)
Your own site
<a href="https://agentmods.dev/skills/rahulkeerthi/expo-toolkit/configuring-expo"><img src="https://agentmods.dev/badge/skills/rahulkeerthi/expo-toolkit/configuring-expo/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.

agentmods 80×15 button for configuring-expo

Your own site · 80×15
<a href="https://agentmods.dev/skills/rahulkeerthi/expo-toolkit/configuring-expo"><img src="https://agentmods.dev/badge/skills/rahulkeerthi/expo-toolkit/configuring-expo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,879 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00036 $0.02879
Opus 5.5 $0.00014 $0.01152
Sonnet 5.5 $0.00007 $0.00576
Haiku 4.5 $0.00004 $0.00288

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

Security

Grade C, and why

configuring-expo scanned grade C with 1 finding 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.

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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf node_modules
skills/configuring-expo/SKILL.md · 530 lines

How it starts

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

Expo Configuration Reference

app.config.js vs app.json

Use app.config.js (recommended):

  • Dynamic configuration based on environment
  • Conditional logic for different build variants
  • Access to environment variables
  • Can import from other files

Use app.json:

  • Simple static configuration
  • No environment-specific needs
  • Quick prototyping

Converting app.json to app.config.js

If you have an existing app.json:

// app.config.js
export default ({ config }) => {
  return {
    ...config,
    // Your customizations here
  };
};

Or start fresh:

// app.config.js
export default {
  name: "My App",
  slug: "my-app",
  // ... rest of config
};

Environment-Specific Bundle IDs

The recommended pattern for running dev/preview/production builds side-by-side on the same device:

// app.config.js
const IS_DEV = process.env.APP_VARIANT === 'development';
const IS_PREVIEW = process.env.APP_VARIANT === 'preview';

const getUniqueIdentifier = () => {
  if (IS_DEV) {
    return 'com.yourcompany.yourapp.dev';
  }
  if (IS_PREVIEW) {
    return 'com.yourcompany.yourapp.preview';
  }
  return 'com.yourcompany.yourapp';
};

const getAppName = () => {
  if (IS_DEV) {
    return 'YourApp (Dev)';
  }
  if (IS_PREVIEW) {
    return 'YourApp (Preview)';
  }
  return 'YourApp';
};

export default {
  name: getAppName(),
  slug: 'your-app',
  version: '1.0.0',
  orientation: 'portrait',
  icon: './assets/icon.png',
  userInterfaceStyle: 'automatic',
  splash: {
    image: './assets/splash.png',
    resizeMode: 'contain',
    backgroundColor: '#ffffff',
  },
  assetBundlePatterns: ['**/*'],
  ios: {
    supportsTablet: true,
    bundleIdentifier: getUniqueIdentifier(),
  },
  android: {
    adaptiveIcon: {
      foregroundImage: './assets/adaptive-icon.png',
      backgroundColor: '#ffffff',
    },
    package: getUniqueIdentifier(),
  },
  web: {
    favicon: './assets/favicon.png',
  },
  extra: {
    eas: {
      projectId: 'your-project-id',
    },
  },
};

Read the full file on GitHub · 530 lines

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. 2mo ago First seen · 530 lines · 36 tokens per session scan C f36fd8f5fbde

Subscribe to this mod's changes

configuring-expo is a skill published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 2,879 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

configuring-expo compared with skills from other repositories

configuring-expo next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
configuring-exporahulkeerthi/expo-toolkitSkill55mo agoMITC36Claude Code
orca-emulator-androidstablyai/orcaSkill117kyesterdayMITA102Claude Code, Codex
glance-canonical-layoutsandroid/skillsSkill10kyesterdayApache-2.0A56Claude Code
android-tombstone-symbolicationdotnet/skillsSkill5.8kyesterdayMITA176Claude Code
dogfoodcallstack/agent-deviceSkill5.3kyesterdayMITA55Claude Code
winapp-mauimicrosoft/winappCliSkill1.4kyesterdayMITA68Claude Code
app_remixrome-os/romeSkill889yesterdayMITA50Claude Code, Codex