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 agentmods add skills/abdullah4ai/apple-developer-toolkit/asc-submission-prereqsnpx skills add Abdullah4AI/apple-developer-toolkit --skill asc-submission-prereqsgit clone --depth 1 https://github.com/Abdullah4AI/apple-developer-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/skills/abdullah4ai/apple-developer-toolkit/asc-submission-prereqs)<a href="https://agentmods.dev/skills/abdullah4ai/apple-developer-toolkit/asc-submission-prereqs"><img src="https://agentmods.dev/badge/skills/abdullah4ai/apple-developer-toolkit/asc-submission-prereqs.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.00042 | $0.02440 |
| Opus 5 | $0.00021 | $0.01220 |
| Sonnet 5 | $0.00008 | $0.00488 |
| Haiku 4.5 | $0.00004 | $0.00244 |
Grade A, and why
asc-submission-prereqs 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 6d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Submission Prerequisites
Complete checklist of everything required before asc submit can succeed. Work through each section in order. Use pre-flight context to skip items already verified.
1. Build Requirements
- Build uploaded and in
VALIDprocessing state - Built with iOS 26 SDK or later (required after April 28, 2026)
- Signing certificate and provisioning profile valid
- Build number unique (higher than any previous upload)
Check: asc builds list --app APP_ID --sort -uploadedDate --limit 1 --output json
2. Required Metadata (per locale)
All fields must be set for each localization:
| Field | Max | Required | Notes |
|---|---|---|---|
| Description | 4000 chars | Yes | First 3 lines visible before "more" |
| Keywords | 100 chars | Yes | Comma-separated, no spaces after commas |
| What's New | 4000 chars | Yes (updates) | Release notes |
| Support URL | URL | Yes | Must be live and accessible |
| Copyright | text | Yes | e.g. "2026 Company Name" |
Check: asc localizations list --version VERSION_ID --output json
3. Privacy Requirements (CRITICAL)
3a. Privacy Policy URL
Required for ALL apps. Must be:
- Publicly accessible URL (not behind login)
- Set in both App Store Connect metadata AND accessible within the app
- Must explicitly state: what data is collected, how, all uses, third-party recipients
Ask user:
A Privacy Policy URL is required for App Store submission. Do you have one?
[OPTIONS]
- Enter URL | [INPUT] Enter your privacy policy URL
- Help me create one | Generate a policy document I can host
- Not sure | Help me determine if I need one
[/OPTIONS]
3b. App Privacy Nutrition Label (Dashboard Only)
Cannot be set via CLI — must be completed in App Store Connect dashboard.
Check pre-flight context for Data collection: detected or not detected.
If data collection is NOT detected:
Tell the user:
Your app doesn't appear to collect user data. Go to App Store Connect > your app > App Privacy > Get Started, and select "No, we do not collect data from this app", then click Publish.
What ships with it
2 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.
- 6d ago First seen · 307 lines · 42 tokens per session scan A 22f90216407b
asc-submission-prereqs is a skill published in the GitHub repository Abdullah4AI/apple-developer-toolkit (10 stars, last pushed 2d ago), licensed MIT. It adds 42 tokens to every session and 2,440 once invoked, about $0.0002 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 skills, from other repositories
play-policy-insights
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and…
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…
account-deletion
Generates an Apple-compliant account deletion flow with multi-step confirmation UI, optional data export, configurable grace period, Keychain cleanup, and server-side deletion request. Use when user needs account deletion, right-to-delete, or Apple App Review compliance for account removal.
consent-flow
Generates GDPR/CCPA/DPDP privacy consent flows with granular category preferences, consent state persistence, audit logging, and ATT (App Tracking Transparency) integration. Use when user needs privacy consent UI, cookie/tracking consent, or compliance management.
appstore-review-checker
Audit iOS/macOS apps against App Store Review Guidelines before submission, with evidence-backed verdicts and fixes. Don't use for Google Play, general code review, or rejection appeals.