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.
npx skills add Xopoko/build-swift-apps --skill appstore-review-readinessgit clone --depth 1 https://github.com/Xopoko/build-swift-appsWrote 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/xopoko/build-swift-apps/appstore-review-readiness)<a href="https://agentmods.dev/skills/xopoko/build-swift-apps/appstore-review-readiness"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/appstore-review-readiness/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/xopoko/build-swift-apps/appstore-review-readiness"><img src="https://agentmods.dev/badge/skills/xopoko/build-swift-apps/appstore-review-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00496 |
| Opus 5 | $0.00026 | $0.00248 |
| Sonnet 5 | $0.00010 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
appstore-review-readiness 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 12d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Review Readiness
Use asc validate and current review commands. Do not use legacy submit-preflight or submit-create shortcuts.
For go/no-go planning, first-submission strategy, or choosing which release skill owns a blocker, use appstore-release-planner first. This skill owns command execution once the review-readiness path is selected.
Preconditions: auth configured; app/version/build IDs resolved; build processing complete unless using --wait; metadata, app info, screenshots, review details, content rights, encryption, pricing, availability, and App Privacy expected complete.
Command Plan Helper
For a deterministic dry-run command plan, run the helper from the plugin root:
python3 "$PLUGIN_ROOT/skills/appstore-review-readiness/scripts/review_readiness_plan.py" \
--app "APP_ID" --version "1.2.3" --platform IOS --build "BUILD_ID" \
--version-id "VERSION_ID" --submission-id "SUBMISSION_ID" \
--metadata-dir "./metadata" --include-submit
The helper prints commands only; it does not call ASC, mutate review state, or read credentials. Pass --json for machine-readable output. Pass --confirming-actions only after manually verifying that generated --confirm commands are intended.
Workflow
- Generate the helper plan unless the user requested one specific command.
- Run read-only readiness checks first: processed build state, normal validate, strict validate, and version-id validate when available.
- Repair blockers in the smallest owning surface: encryption, content rights, metadata, screenshots, IAP/subscriptions, or App Privacy.
- Submit only after dry-run output is clean and the user has clearly selected the build/version to send.
- Monitor by app, version ID, or submission ID; cancel only when the active submission is identified and the user intends cancellation.
For macOS App Store review, use the same flow with --platform MAC_OS.
References
references/appstore-review-readiness.mdfor detailed ASC repair, submit, multi-item submission, monitor, and retry commands.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 40 lines · 51 tokens per session scan A 1939c7c15f33
appstore-review-readiness is a skill published in the GitHub repository Xopoko/build-swift-apps (45 stars, last pushed 14d ago), licensed MIT. It adds 51 tokens to every session and 496 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-30.
Other skills, from other repositories
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
firebase-messaging
Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).
generate-images-with-firebase-ai
Use when generating or editing images from Flutter/Dart with Firebase AI Logic and a Gemini image model (Nano Banana), making the first call work, choosing Gemini Developer API vs Vertex AI, hitting quota, billing or App Check failures, getting empty or image-only responses, sending a user photo as input, controlling…
firebase-app-check
Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.
flutter-app-architecture
Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).
firebase-ai
Use when setting up firebaseai, generating text/chat with Gemini, streaming AI output, building multimodal prompts, or handling AI errors.