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 vishalvshekkar/app-store-toolkit --skill privacygit clone --depth 1 https://github.com/vishalvshekkar/app-store-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/vishalvshekkar/app-store-toolkit/privacy)<a href="https://agentmods.dev/skills/vishalvshekkar/app-store-toolkit/privacy"><img src="https://agentmods.dev/badge/skills/vishalvshekkar/app-store-toolkit/privacy.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.00016 | $0.01138 |
| Opus 5 | $0.00008 | $0.00569 |
| Sonnet 5 | $0.00003 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
app-store-toolkit:privacy 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/app-store-toolkit:privacy
You are analyzing the app's source code to help generate the App Privacy "nutrition label" required by Apple.
Background
Apple requires all apps to declare their privacy practices via "App Privacy" labels in App Store Connect. These labels cover:
- Data Collection: What data types the app collects
- Data Use: How collected data is used (analytics, advertising, product personalization, etc.)
- Data Linking: Whether data is linked to the user's identity
- Data Tracking: Whether data is used for cross-app tracking
Steps
1. Determine Source Path
Use $ARGUMENTS for a custom path, or default to the current project root.
2. Scan Source Code
Search the codebase for patterns indicating data collection:
Contact Info:
- Email:
NSContactsUsageDescription, email fields, contact forms - Phone: phone number inputs,
CNContact - Address: address fields, location permissions for address
Health & Fitness:
HealthKit,HKHealthStore, workout data
Financial:
- Payment APIs,
StoreKit, credit card fields,PKPayment
Location:
CLLocationManager,CoreLocation,MapKit, GPS coordinates- Precise vs approximate location
Sensitive Info:
- Biometric data:
LocalAuthentication,LAContext, Face ID, Touch ID
Contacts:
CNContactStore, address book access
User Content:
- Photos:
PHPhotoLibrary,UIImagePicker, camera access - Files: document pickers, file uploads
- Audio/Video: microphone, camera recording
Browsing History:
WKWebView,SFSafariViewController, URL tracking
Search History:
- Search bar inputs, search analytics
Identifiers:
identifierForVendor,advertisingIdentifier, IDFA- Device fingerprinting patterns
- User IDs, account creation
Usage Data:
- Analytics SDKs: Firebase, Amplitude, Mixpanel, Segment
- Crash reporting: Crashlytics, Sentry, Bugsnag
- Custom analytics events
Diagnostics:
- Crash logs, performance data
MetricKit, diagnostic reports
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 · 157 lines · 16 tokens per session scan A 1796232bd278
app-store-toolkit:privacy is a skill published in the GitHub repository vishalvshekkar/app-store-toolkit (5 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,138 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 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…
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.
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.
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.