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-dev-clientgit 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-dev-client)<a href="https://agentmods.dev/skills/fatihkan/badi/expo-dev-client"><img src="https://agentmods.dev/badge/skills/fatihkan/badi/expo-dev-client.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
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 →
- medium MCP Rug Pull · line 31 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 62 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 63 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 84 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 86 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 173 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00068 | $0.01330 |
| Opus 5 | $0.00034 | $0.00665 |
| Sonnet 5 | $0.00014 | $0.00266 |
| Haiku 4.5 | $0.00007 | $0.00133 |
Grade A, and why
expo-dev-client 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 yesterday.
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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
expo-dev-client
Setting up custom development builds with expo-dev-client. Comparison with Expo Go, build profiles, a custom dev menu, runtime-version compatibility, and the EAS Update test flow.
What It Does
expo-dev-clientsetup + build profile- Expo Go vs Dev Client decision
- Dev menu (cmd+D / shake) and custom actions
- Dev launcher (multi-app, multi-server)
- EAS Update test flow (via the dev client)
- Runtime version & native dep compatibility
Setup
npx expo install expo-dev-client
app.json (automatic plugin):
{
"expo": {
"plugins": ["expo-dev-client"]
}
}
EAS profile:
{
"build": {
"development": {
"developmentClient": true,
"distribution": "internal",
"ios": { "simulator": true },
"channel": "development"
}
}
}
Build:
eas build --profile development --platform ios
eas build --profile development --platform android
# or local
npx expo run:ios
npx expo run:android
Expo Go vs Dev Client
| Feature | Expo Go | Dev Client |
|---|---|---|
| Setup | From the App Store | Your own build |
| Native module | Only Expo SDK | All custom modules |
| Config plugin | Limited | Full support |
| Bundle ID | host.exp.Exponent | Your own ID |
| Splash/icon | Generic | Your own |
| EAS Update | ❌ | ✅ |
| Push notification | Limited | Full support |
| Production-like | No | Yes |
In modern Expo the default recommendation is Dev Client. Expo Go is for quick prototyping only.
Start the Dev Server
npx expo start --dev-client
# or
npx expo start
# → the "dev client" option appears in the QR menu
Once the Dev Client app opens:
- Show the server URL (LAN/Tunnel)
- Scan the QR or enter the URL manually
- The bundle loads
Dev Launcher
With the Dev Client's Switch to another bundle:
- Connect to a different dev server (collab)
- Preview an EAS Update branch
- Preview the production bundle (rare)
Dev Menu
Trigger:
- iOS sim:
Cmd+DorCmd+Ctrl+Z - Android emulator:
Cmd+M/Ctrl+M - Device: shake
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.
- yesterday First seen · 199 lines · 68 tokens per session scan A 968ad0f2f3bd
expo-dev-client is a skill published in the GitHub repository fatihkan/badi (7 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 1,330 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-09-06.
Other skills, from other repositories
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…
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.
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.
review-pr
Perform a comprehensive code review of a pull request.
release-notes
Generate release notes in multiple formats from git commits.