Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/fatihkan/badinpx agentmods add skills/fatihkan/badi/expo-eas-buildWrote 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/fatihkan/badi/expo-eas-build)<a href="https://agentmods.dev/skills/fatihkan/badi/expo-eas-build"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-eas-build/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/fatihkan/badi/expo-eas-build"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-eas-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.01575 |
| Opus 5 | $0.00037 | $0.00788 |
| Sonnet 5 | $0.00015 | $0.00315 |
| Haiku 4.5 | $0.00007 | $0.00158 |
Grade A, and why
expo-eas-build 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.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-eas-build
A guide to profile discipline, credentials management, and the build process for EAS Build. Scoped to eas.json configuration, iOS provisioning + push cert, Android keystore + service account, secrets, and monorepo support. Store-submit DETAIL lives in expo-eas-submit.
What It Does
eas.jsonprofile architecture (development / preview / production)- iOS credentials: provisioning profile, distribution cert, push cert
- Android credentials: keystore, upload key, FCM service account
- Build cache, environment variables, EAS Secrets
- Build hooks (
eas-build-pre-install,eas-build-on-success) - Monorepo (
pnpm/yarn workspaces/turborepo) support
Setup
npm install -g eas-cli
eas login
eas whoami
eas init # assigns the project ID
eas build:configure # eas.json starter
eas.json Template
{
"cli": { "version": ">= 7.0.0", "appVersionSource": "remote" },
"build": {
"base": {
"node": "20.11.0",
"env": { "EXPO_PUBLIC_APP_ENV": "base" }
},
"development": {
"extends": "base",
"developmentClient": true,
"distribution": "internal",
"ios": { "simulator": true },
"channel": "development"
},
"preview": {
"extends": "base",
"distribution": "internal",
"android": { "buildType": "apk" },
"channel": "preview",
"env": { "EXPO_PUBLIC_APP_ENV": "preview" }
},
"production": {
"extends": "base",
"autoIncrement": true,
"channel": "production",
"env": { "EXPO_PUBLIC_APP_ENV": "production" }
}
},
"submit": { "production": {} }
}
Profile Strategy
| Profile | Distribution | Purpose | Device |
|---|---|---|---|
| development | internal | Dev client, JS debug, hot reload | Device/sim |
| preview | internal | QA/stakeholder test (IPA/APK) | Device |
| production | store | App Store / Play Store | Device |
iOS Credentials
eas credentials # interactive menu
eas credentials -p ios # iOS only
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.
- 4d ago First seen · 223 lines · 75 tokens per session scan A 0d7e889aa4ac
expo-eas-build is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 1,575 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
eval-agents
Audit Claude Code agents defined in .claude/agents/ for description specificity, model tier appropriateness, tools scoping, and system prompt quality. Detects dispatch ambiguity between agents, flags over-permissive tool grants, and checks for human-in-the-loop patterns that break programmatic orchestration. Use when…
review-pr
Perform a comprehensive code review of a pull request.
landing-page-generator
Generate complete, deploy-ready landing pages from any repository. Use when creating a homepage for an open-source project, building a project website, converting a README into a marketing page, or standardizing landing pages across multiple repos.
talk-stage5-script
Produces a complete 5-act pitch with speaker notes, a slide-by-slide specification, and a ready-to-paste Kimi prompt for AI slide generation. Requires validated angle and title from Stage 4. Use when you have a confirmed talk angle and need the full script, slide spec, and AI-generated presentation prompt.