Borrowing it
Nothing to install: this file belongs to JasonColapietro/ios-app-dev-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JasonColapietro/ios-app-dev-skills/main/.claude/commands/ios-submit-check.mdgit clone --depth 1 https://github.com/JasonColapietro/ios-app-dev-skillsWrote 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/commands/jasoncolapietro/ios-app-dev-skills/ios-submit-check)<a href="https://agentmods.dev/commands/jasoncolapietro/ios-app-dev-skills/ios-submit-check"><img src="https://agentmods.dev/badge/commands/jasoncolapietro/ios-app-dev-skills/ios-submit-check/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/commands/jasoncolapietro/ios-app-dev-skills/ios-submit-check"><img src="https://agentmods.dev/badge/commands/jasoncolapietro/ios-app-dev-skills/ios-submit-check.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.00015 | $0.00174 |
| Opus 5 | $0.00008 | $0.00087 |
| Sonnet 5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00017 |
Grade A, and why
ios-submit-check 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 9d 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.
What it actually says
/ios-submit-check
Input: $ARGUMENTS - app project, archive path, version/build, or release brief.
Use ios-app-store-release, ios-aso-launch, ios-screenshot-taker,
ios-swiftui-product, and site-to-ios-app when the app came from a site.
Block submission until:
- release build passes;
- bundle ID, version, build, signing, and account are identified;
- metadata passes limits and feature truth;
- screenshots exist and match the actual app;
- privacy answers and review notes are ready;
- no secrets or signing artifacts are staged;
- the user explicitly delegates upload or submission.
Output PASS or BLOCK, exact blockers, and the next command to run.
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.
- 9d ago First seen · 23 lines · 15 tokens per session scan A 766d76378a7e
ios-submit-check is a command published in the GitHub repository JasonColapietro/ios-app-dev-skills (2 stars, last pushed 2d ago), licensed MIT. It adds 15 tokens to every session and 174 once invoked, about $0.0001 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 commands, from other repositories
privacy-check
Scan for required-reason API usage and verify PrivacyInfo.xcprivacy completeness before submission.
check-build
Check CI build status and debug failures via App Store Connect MCP.
msd-setup-credentials
Interactive credential setup for App Store and Google Play — walks through getting each key, validates format, and stores securely in EAS secrets or .env.production.
msd-release
Run the full mobile app release pipeline for iOS and/or Android.
msd-release-notes
Generate "What's New" release notes for all locales — outputs a single consolidated file per platform with locale XML tags for easy copy-paste.
msd-permissions
Validate and fix iOS and Android app permissions — checks NSUsageDescription strings, Android dangerous permissions, and optionally modifies app.json.