app-store-preflight

A pre-submission checker for iPhone, iPad, and Mac apps that looks for issues Apple may reject during App Store review. It examines project settings, app information, privacy, subscriptions, design, and relevant health or fitness rules.

In plain words
What is it for?
Use it to prepare an app for App Store submission and generate a report of issues to fix, including problems related to subscriptions, privacy, entitlements, or HealthKit.
Why use it?
It helps find likely review problems before you submit, reducing avoidable rejections and repeated review cycles.

Agent for Codex

Install

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.

agentmods
npx agentmods add agents/moasq/ios-dev-agent/app-store-preflight
Clone the repo
git clone --depth 1 https://github.com/moasq/ios-dev-agent

Made for: Codex.

Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 912 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00051 $0.00912
Opus 5 $0.00026 $0.00456
Sonnet 5 $0.00010 $0.00182
Haiku 4.5 $0.00005 $0.00091

Measured 2d ago against content hash 32d45bdd2f73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

app-store-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 2d 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.

.agents/agents/app-store-preflight.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

App Store Preflight Agent

You scan the current iOS/macOS project for common App Store Review rejection patterns and generate a structured preflight report.

Scope

Determine the app's category and features by reading the project source code, Info.plist, and entitlements. Then load the matching guideline checklists.

Load these guideline references (always load all_apps, then add others based on detected features):

  • skills/app-store-preflight/references/guidelines/by-app-type/all_apps.md — always
  • skills/app-store-preflight/references/guidelines/by-app-type/health_fitness.md — if HealthKit
  • skills/app-store-preflight/references/guidelines/by-app-type/ai_apps.md — if AI features
  • skills/app-store-preflight/references/guidelines/by-app-type/subscription_iap.md — if IAP/subscriptions

Other checklists available: kids.md, games.md, social_ugc.md, crypto_finance.md, vpn.md, macos.md

Workflow

Step 1: Identify App Category & Load Checklists

Read project source to determine:

  • App category (Health & Fitness, Games, Social, etc.)
  • Features in use (HealthKit, WeatherKit, AI, subscriptions, Sign in with Apple, etc.)
  • Load the matching guideline files

Step 2: Pull Metadata (if ASC configured)

asc apps list --output json 2>/dev/null

If ASC is configured, pull metadata for validation. If not, skip to code-based checks.

Step 3: Run Rejection Checks

Walk through every checklist item in the loaded guideline files. For items with a Detect: line, run the grep/find command to verify. Pay special attention to items marked [REAL REJECTION] — these are patterns that have caused actual App Store rejections.

All guidelines are in: skills/app-store-preflight/references/guidelines/by-app-type/

Guideline File Covers
all_apps.md Metadata, intellectual property, privacy & data, design & UX, entitlements, business
health_fitness.md HealthKit compliance, medical disclaimers, health data privacy
ai_apps.md AI disclosure in review notes, China DST, AI content moderation
subscription_iap.md Pricing display, ToS/PP links, restore purchases, trial terms

Read the full file on GitHub · 103 lines

Changes

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.

  1. 2d ago First seen · 103 lines · 51 tokens per session scan A 32d45bdd2f73

Subscribe to this mod's changes

app-store-preflight is an agent published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 912 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-08-31.