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 fatihkan/badi --skill expo-eas-submitgit clone --depth 1 https://github.com/fatihkan/badiWrote 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-submit)<a href="https://agentmods.dev/skills/fatihkan/badi/expo-eas-submit"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-eas-submit.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Privilege Escalation · line 102 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.01572 |
| Opus 5 | $0.00037 | $0.00786 |
| Sonnet 5 | $0.00015 | $0.00314 |
| Haiku 4.5 | $0.00007 | $0.00157 |
Grade A, and why
expo-eas-submit 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 2d 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 — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-eas-submit
A guide to the App Store Connect (iOS) and Google Play Console (Android) submit process with EAS Submit. Metadata management, build-artifact selection, review notes, and phased-release discipline. Build-profile DETAIL lives in expo-eas-build.
What It Does
- Uploading iOS/Android builds with
eas submit - App Store Connect API Key (ASC) and Google Play Service Account setup
- Build artifact selection (latest / specific URL / specific ID)
- Review notes and demo-account management
- Phased release / staged rollout
- Screenshot and metadata upload discipline
Setup
eas submit:configure
eas.json Submit Section
{
"submit": {
"production": {
"ios": {
"ascAppId": "1234567890",
"appleTeamId": "ABCDE12345",
"ascApiKeyPath": "./credentials/AuthKey_XXX.p8",
"ascApiKeyId": "XXX",
"ascApiKeyIssuerId": "yyy-yyy-yyy"
},
"android": {
"serviceAccountKeyPath": "./credentials/play-service-account.json",
"track": "internal",
"releaseStatus": "draft",
"rollout": 0.1,
"changesNotSentForReview": false
}
},
"preview": {
"android": { "track": "internal" }
}
}
}
iOS Submit Flow
# 1. Upload the latest build
eas submit --platform ios --profile production --latest
# 2. Specific build ID
eas submit -p ios --id <build-id>
# 3. Upload a local IPA
eas submit -p ios --path ./build.ipa
ASC API Key (recommended)
App Store Connect > Users and Access > Integrations > App Store Connect API:
- Key ID, Issuer ID,
.p8file - Role: App Manager (enough for submit)
Store ascApiKeyPath in eas.json or on the EAS server.
TestFlight Flow
- Submit completes successfully → ASC > TestFlight > Processing
- Answer the compliance questions (encryption usage)
- Add an internal testing group
- Beta Review is required for external testing
Android Submit Flow
eas submit -p android --profile production --latest
eas submit -p android --path ./app.aab
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.
- 2d ago First seen · 214 lines · 75 tokens per session scan A 6e2cc97d42be
expo-eas-submit is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 1,572 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.
plan-pipeline
Orchestrates the complete planning pipeline: product direction (ceo-review) -> architecture (eng-review) -> implementation plan (start) -> validation (validate) -> execution (execute). Run stages individually or let the orchestrator coordinate the full flow.
handoff-resume
Load a handoff document and resume work from where a previous session left off. Parses scope, file references, completed work, and next steps, then confirms understanding before proceeding.
atlas-complete
Complete the current milestone and prepare next work by following the canonical complete command doc.
atlas-init
Initialize project with CLAUDE.md, STATE.md, and ROADMAP.md by following the canonical init command doc.
atlas-triage
Pull and triage issues from external sources for planning by following the canonical triage command doc.