Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add rahulkeerthi/expo-toolkit/plugin install expo-toolkitWrote 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/rahulkeerthi/expo-toolkit/submitting-android)<a href="https://agentmods.dev/skills/rahulkeerthi/expo-toolkit/submitting-android"><img src="https://agentmods.dev/badge/skills/rahulkeerthi/expo-toolkit/submitting-android.svg" alt="Measured on agentmods" 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.00037 | $0.02326 |
| Opus 5 | $0.00018 | $0.01163 |
| Sonnet 5 | $0.00007 | $0.00465 |
| Haiku 4.5 | $0.00004 | $0.00233 |
Grade A, and why
submitting-android 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 6d 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 — 373 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Play Console Submission Reference
Plugin Tools
Validate your store assets before submission:
# Check Android assets (icon, feature graphic, screenshots)
cd /path/to/expo-toolkit && npm run validate-assets -- --android
# Or directly
node tools/validate-store-assets.js --android
node tools/validate-store-assets.js --android --json
This validates:
- App icon (512x512 minimum)
- Feature graphic (1024x500)
- Screenshot dimensions and count (minimum 2)
Testing Tracks Overview
Google Play provides multiple testing tracks before production release:
| Track | Testers | Review Time | Use Case |
|---|---|---|---|
| Internal | Up to 100 | Instant | Quick smoke testing, core team |
| Closed | Limited list | 3-5 days | Beta testers, stakeholder review |
| Open | Anyone can join | 3-5 days | Public beta, wide feedback |
| Production | All users | 1-7 days | Full public release |
Internal Testing (Recommended Start)
- Maximum testers: 100 (you choose them)
- Availability: Instant (no review)
- Best for: Quick iteration, smoke testing
- Note: Can start before completing all store listing requirements
Closed Testing
- Testers: You create and manage tester lists
- Availability: After Google review (3-5 days)
- Best for: Controlled beta testing
- Note: Required for personal accounts before production (12+ testers, 14+ days)
Open Testing
- Testers: Anyone can join via Play Store
- Availability: After Google review
- Best for: Wide feedback collection
- Note: Shows as "Early access" in Play Store
Production
- Users: All Play Store users
- Availability: After Google review
- Best for: Public release
- Note: First review typically longer (7+ days)
First-Time Submission Requirements
For ALL New Apps
- Manual AAB Upload Required
- First build must be manually uploaded
- Download AAB from EAS:
eas build --platform android --profile production - Upload to Play Console → Release → Production → Create release
- After first release, EAS
--auto-submitworks
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.
- 6d ago First seen · 373 lines · 37 tokens per session scan A 88ee6d171312
submitting-android is a skill published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 2,326 once invoked, about $0.0002 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
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.