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/rahulkeerthi/expo-toolkitnpx agentmods add skills/rahulkeerthi/expo-toolkit/submitting-androidWrote 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/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/rahulkeerthi/expo-toolkit/submitting-android"><img src="https://agentmods.dev/badge/skills/rahulkeerthi/expo-toolkit/submitting-android.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.00037 | $0.02326 |
| Opus 5.5 | $0.00015 | $0.00930 |
| Sonnet 5.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 2mo 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.
- 2mo 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 5mo ago), licensed MIT. It adds 37 tokens to every session and 2,326 once invoked, about $0.0001 per session on Opus 5.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.
submitting-android compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| submitting-androidrahulkeerthi/expo-toolkit | Skill | 5 | 5mo ago | MIT | A | 37 | Claude Code |
| orca-emulator-androidstablyai/orca | Skill | 117k | yesterday | MIT | A | 102 | Claude Code, Codex |
| glance-canonical-layoutsandroid/skills | Skill | 10k | yesterday | Apache-2.0 | A | 56 | Claude Code |
| android-tombstone-symbolicationdotnet/skills | Skill | 5.8k | yesterday | MIT | A | 176 | Claude Code |
| dogfoodcallstack/agent-device | Skill | 5.3k | yesterday | MIT | A | 55 | Claude Code |
| winapp-mauimicrosoft/winappCli | Skill | 1.4k | yesterday | MIT | A | 68 | Claude Code |
| app_remixrome-os/rome | Skill | 889 | yesterday | MIT | A | 50 | Claude Code, Codex |