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 skills add Ampli-Group/agentic-mobile-blueprint --skill eas-mobile-deploymentgit clone --depth 1 https://github.com/Ampli-Group/agentic-mobile-blueprintWrote 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/ampli-group/agentic-mobile-blueprint/eas-mobile-deployment)<a href="https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/eas-mobile-deployment"><img src="https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/eas-mobile-deployment/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.
<a href="https://agentmods.dev/skills/ampli-group/agentic-mobile-blueprint/eas-mobile-deployment"><img src="https://agentmods.dev/badge/skills/ampli-group/agentic-mobile-blueprint/eas-mobile-deployment.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01677 |
| Opus 5 | $0.00026 | $0.00839 |
| Sonnet 5 | $0.00010 | $0.00335 |
| Haiku 4.5 | $0.00005 | $0.00168 |
Grade A, and why
eas-mobile-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 10d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EAS Mobile Deployment
How It Works
BUILD and SUBMIT are independent EAS services. A build creates the binary. A submit uploads an existing binary to a store. They never need to run together.
eas buildcreates an IPA (iOS) or AAB (Android) and stores it on EASeas submittakes an existing build artifact and uploads it to App Store Connect or Google Play- A single build can be submitted multiple times (e.g. first to internal track, then to production)
- A failed submission does not require a rebuild
Distribution Settings (CRITICAL)
The distribution field controls build type, but does NOT automatically upload to stores:
| Setting | Purpose | Required For |
|---|---|---|
"distribution": "store" |
Creates store-ready binaries | App Store / Play Store submissions |
Important: distribution: "store" alone does NOT upload to stores. You must explicitly submit builds using a separate eas submit command after the build completes.
CI/CD Pattern: Split build and submit into separate jobs:
- Build job:
eas build --platform ios --profile production --non-interactive - Submit job:
eas submit --platform ios --profile production --latest --non-interactive
This allows builds to succeed even if submission fails, and enables retrying submissions without rebuilding.
Version Management
Two separate version concepts:
| Version | Where | Who manages | Purpose |
|---|---|---|---|
version |
app.json | You, manually | User-facing (e.g. 1.2.0). Shown on App Store / Play Store. |
buildNumber / versionCode |
EAS remote | EAS, automatically | Developer-facing. Must be unique per store upload. Auto-incremented. |
This is controlled by two eas.json fields:
appVersionSource: "remote"-- EAS stores build numbers on its servers, not in local files. Required for CI/CD where builds happen on different machines/branches.autoIncrement: true(on the build profile) -- EAS bumps the build number on every build. You never touch it.
What ships with it
1 file 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.
- 10d ago First seen · 142 lines · 52 tokens per session scan A fd09e9935201
eas-mobile-deployment is a skill published in the GitHub repository Ampli-Group/agentic-mobile-blueprint (4 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 1,677 once invoked, about $0.0003 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
rn-app-builder
A build workflow for React Native mobile apps, including Expo setup, shared code in a monorepo, login routing, APIs, themes, and releases. A monorepo stores multiple related packages in one code repository.
native-ui
Building native mobile UIs with Expo Router and React Native. Covers routing, navigation, styling, native controls, animations, and platform conventions following Apple Human Interface Guidelines.
expo-native-ui
Build beautiful native iOS/Android apps with Expo Router. Covers route structure, native tabs, animations, blur effects, liquid glass, SF Symbols, and platform patterns.
writing-react-native-storybook-stories
Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for…
setup-react-native-storybook
Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a…
uniwind
Uniwind — Tailwind CSS v4 styling for React Native. Use when adding, building, or debugging components in a React Native project that uses Uniwind classNames. Covers setup, Metro config, global.css, theming, className props, accent- color props, platform/data/state/responsive variants, CSS variables, custom utilities…