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/cruisediary/apple-app-review-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/cruisediary/apple-app-review-skills/appstore-detect)<a href="https://agentmods.dev/commands/cruisediary/apple-app-review-skills/appstore-detect"><img src="https://agentmods.dev/badge/commands/cruisediary/apple-app-review-skills/appstore-detect/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/cruisediary/apple-app-review-skills/appstore-detect"><img src="https://agentmods.dev/badge/commands/cruisediary/apple-app-review-skills/appstore-detect.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.00000 | $0.00720 |
| Opus 5 | $0.00000 | $0.00360 |
| Sonnet 5 | $0.00000 | $0.00144 |
| Haiku 4.5 | $0.00000 | $0.00072 |
Grade A, and why
appstore-detect 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 7d 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
App Store Project Detection
Quick terminal commands to inspect your iOS project before running a full audit.
Project Info
Run !find . -name "Info.plist" -not -path "*/Pods/*" -not -path "*/.build/*" to locate Info.plist files.
Run !find . -name "PrivacyInfo.xcprivacy" -not -path "*/Pods/*" to check Privacy Manifest existence.
Run !find . -name "*.xcodeproj" -o -name "*.xcworkspace" | head -5 to identify project type.
iOS Version & Build Config
Run !grep -r "IPHONEOS_DEPLOYMENT_TARGET\|MARKETING_VERSION\|CURRENT_PROJECT_VERSION" . --include="*.pbxproj" | head -10 to check deployment target and version.
Run !find . -name "Info.plist" -not -path "*/Pods/*" | head -1 | xargs plutil -convert json -o - | python3 -c "import sys,json; d=json.load(sys.stdin); print('Name:', d.get('CFBundleDisplayName', d.get('CFBundleName'))); print('Version:', d.get('CFBundleShortVersionString')); print('Bundle ID:', d.get('CFBundleIdentifier'))" to show app name, version, and bundle ID.
Permissions Summary
Run !find . -name "Info.plist" -not -path "*/Pods/*" | head -1 | xargs plutil -convert json -o - | python3 -c "import sys,json; [print(k, '=', repr(v[:60])+'...') for k,v in json.load(sys.stdin).items() if 'UsageDescription' in k]" to list all permission descriptions.
Run !grep -rn "requestAuthorization\|requestWhenInUseAuthorization\|requestAlwaysAuthorization\|requestTrackingAuthorization" . --include="*.swift" | wc -l to count permission requests.
Privacy Manifest
Run !find . -name "PrivacyInfo.xcprivacy" -not -path "*/Pods/*" to check if PrivacyInfo.xcprivacy exists (required since May 2024).
Run !grep -rn "UserDefaults\|identifierForVendor\|mach_absolute_time" . --include="*.swift" | grep -v "//" | wc -l to count required-reason API usages.
Account Deletion (Required since June 2022)
Run !grep -rn "deleteAccount\|Delete Account\|destroyAccount" . --include="*.swift" to check account deletion implementation.
IAP & Subscriptions
Run !grep -rn "StoreKit\|SKPayment\|Product.purchase" . --include="*.swift" | wc -l to check StoreKit usage.
Run !grep -rn "Stripe\|PayPal\|paypal\|braintree" . --include="*.swift" -i to check for prohibited external payments.
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.
- 7d ago First seen · 34 lines · 0 tokens per session scan A a6405460bd79
appstore-detect is a command published in the GitHub repository cruisediary/apple-app-review-skills (16 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 720 tokens. 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-09-05.
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.
feature-build
Build a complete mobile feature from description to running code with E2E tests. Orchestrates 6 phases - planning, implementation, testing, build-fix, quality gate, and verification. Auto-detects platform.
preflight
Audit a build against App Review rejection triggers by app type before submitting.
fix-build
Diagnose and fix Xcode build failures (launches build-fixer agent).
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.