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.
git clone --depth 1 https://github.com/rahulkeerthi/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/commands/rahulkeerthi/expo-toolkit/ios-preflight)<a href="https://agentmods.dev/commands/rahulkeerthi/expo-toolkit/ios-preflight"><img src="https://agentmods.dev/badge/commands/rahulkeerthi/expo-toolkit/ios-preflight.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.00019 | $0.07443 |
| Opus 5 | $0.00010 | $0.03721 |
| Sonnet 5 | $0.00004 | $0.01489 |
| Haiku 4.5 | $0.00002 | $0.00744 |
Grade A, and why
ios-preflight 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 8d 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 — 1,036 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS App Store Connect Pre-flight Check
Validate App Store Connect configuration before submission to catch common rejection reasons.
Setup Questionnaire
Before running checks, gather information about the user's setup using AskUserQuestion:
AskUserQuestion({
questions: [
{
question: "What is your app's monetization model?",
header: "Monetization",
options: [
{
label: "Freemium (IAP/Subscriptions)",
description: "Free download with in-app purchases or subscriptions",
},
{
label: "Paid Upfront",
description: "One-time purchase price to download the app",
},
{
label: "Free (No IAP)",
description: "Completely free with no monetization",
},
],
multiSelect: false,
},
{
question: "Which paywall implementation are you using?",
header: "Paywall",
options: [
{
label: "RevenueCat Paywalls",
description: "RC's built-in paywall UI (Freemium only)",
},
{
label: "Custom Implementation",
description: "Custom paywall UI with RC SDK (Freemium only)",
},
{
label: "No Paywall",
description: "No subscription UI (select if Free or Paid Upfront)",
},
],
multiSelect: false,
},
{
question: "Is your app universal (supports iPad)?",
header: "iPad",
options: [
{
label: "iPhone Only",
description: "App only runs on iPhone",
},
{
label: "Universal (iPhone + iPad)",
description: "App runs on both iPhone and iPad",
},
],
multiSelect: false,
},
],
});
Conditional Checks Based on Setup
Based on user responses, adjust the validation:
| Monetization | Skip These Checks |
|---|---|
| Free (No IAP) | IAP validation, RevenueCat cross-check, Paywall check |
| Paid Upfront | IAP validation, RevenueCat cross-check, Paywall check |
| Freemium | Run all checks |
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.
- 8d ago First seen · 1,036 lines · 19 tokens per session scan A 81e6a07808d1
ios-preflight is a command published in the GitHub repository rahulkeerthi/expo-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 7,443 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
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
initialize-ios
Manual override: initialize ast-index for iOS/Swift/ObjC project.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
mobile-performance-check
Analyze mobile app for performance issues using the mobile-best-practices database.
flutter-review
Review Flutter/Dart code for idiomatic patterns, widget best practices, state management, performance, accessibility, and security. Invokes the flutter-reviewer agent.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.