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 rshankras/claude-code-apple-skills --skill custom-product-pagesgit clone --depth 1 https://github.com/rshankras/claude-code-apple-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/skills/rshankras/claude-code-apple-skills/custom-product-pages)<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/custom-product-pages"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/custom-product-pages/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/rshankras/claude-code-apple-skills/custom-product-pages"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/custom-product-pages.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.00048 | $0.02533 |
| Opus 5 | $0.00024 | $0.01267 |
| Sonnet 5 | $0.00010 | $0.00507 |
| Haiku 4.5 | $0.00005 | $0.00253 |
Grade A, and why
custom-product-pages 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 11d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Custom Product Pages Generator
Generate metadata templates for Custom Product Pages (CPPs) — targeted App Store product page variants optimized for specific audiences, ad campaigns, or traffic sources.
When This Skill Activates
Use this skill when the user:
- Asks to create "custom product pages" or "targeted App Store pages"
- Mentions "different App Store pages for different audiences"
- Wants to create pages for specific ad campaigns (Apple Search Ads, social media)
- Asks about A/B testing product page messaging
- Has multiple user personas and wants tailored messaging
Minimum Eligibility
CPPs only make sense when you have enough traffic to meaningfully split across pages.
| Monthly Impressions | Recommendation |
|---|---|
| Under 2,000 | Don't create CPPs. Focus on optimizing your single default page. You won't have enough traffic per page to know if it's working. |
| 2,000-10,000 | Create 1 CPP max for your most distinct audience segment or highest-spend ad campaign. Monitor for 4+ weeks. |
| 10,000-50,000 | Create 2-3 CPPs. Enough traffic to compare performance across pages. |
| 50,000+ | Full CPP strategy. Multiple pages per segment, ad campaign-specific pages, seasonal variants. |
Exception: If you're running paid Apple Search Ads campaigns, CPPs are valuable even at lower organic volume because ad traffic is directed specifically to your CPP — you're not splitting organic impressions.
How Custom Product Pages Work
- You can create up to 35 custom product pages per app — prioritize a few distinctive pages over filling all 35
- Each page gets a unique URL: your default App Store link plus a product-page-ID parameter; devices below iOS 15 (or a disabled page) fall back to the default page
- You can customize: screenshots, app previews, and promotional text
- The app icon, name, subtitle, and description remain the same across all pages
- Each page is fully localizable, independently of the default page
- Available on iOS 15+ and macOS 12+; the App Store Connect API automates page creation at scale
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.
- 11d ago First seen · 256 lines · 48 tokens per session scan A 03f9d16c51fa
custom-product-pages is a skill published in the GitHub repository rshankras/claude-code-apple-skills (719 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 2,533 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-30.
Other skills, from other repositories
android-development
Android development with Kotlin, Jetpack Compose, and modern Android architecture. Use when building Android apps, implementing Material Design, or following Android best practices.
flutter-development
Cross-platform development with Flutter and Dart for iOS, Android, Web, Desktop, and embedded. Use when building Flutter apps, implementing Material/Cupertino design, or optimizing Dart code.
ios-development
Comprehensive guide for building native Apple platform applications.
kotlin-multiplatform
KMP/CMP shared business logic, Compose Multiplatform, expect/actual, Ktor, SQLDelight, and platform-specific implementations. Use when building cross-platform Kotlin applications for Android, iOS, desktop, or web.
flame-harness-admob
Phase 7 — analyze the game, decide a rewarded-ad strategy, guide manual AdMob ad-unit creation, and inject googlemobileads + ATT/UMP consent code.
flame-harness-screenshot
Phase 9 — capture store screenshots in the game's configured locales via integrationtest (ads hidden), fill ASO keywords, and upload via fastlane.