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 markdavidgan/apple-dev-skills --skill paywall-designgit clone --depth 1 https://github.com/markdavidgan/apple-dev-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/markdavidgan/apple-dev-skills/paywall-design)<a href="https://agentmods.dev/skills/markdavidgan/apple-dev-skills/paywall-design"><img src="https://agentmods.dev/badge/skills/markdavidgan/apple-dev-skills/paywall-design.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.00124 | $0.01167 |
| Opus 5 | $0.00062 | $0.00583 |
| Sonnet 5 | $0.00025 | $0.00233 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
paywall-design 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 4d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Paywall Design
Design paywalls that convert without getting rejected. Economics (tiers, regional pricing) live in app-store-pricing; the implementation lives in storekit-purchases; this is the screen — UX and compliance.
App Review compliance — non-negotiable (Guideline 3.1.2)
A paywall that converts but gets rejected ships nothing. Every subscription paywall must show, on the purchase screen or one tap away:
- What the user gets (the value/contents of the subscription).
- Price, duration, and per-period billing for each option (e.g. "$4.99/month").
- For free trials / intro offers: the trial length, what happens when it ends, and the price that begins — clearly, before purchase.
- A visible Restore Purchases control.
- Functional links to Terms (EULA) and Privacy Policy.
- Honest auto-renew disclosure (it renews until cancelled).
Missing any of these is the most common subscription rejection. Build the compliant skeleton first, then design on top of it.
The conversion structure (top to bottom)
- Value first, price second. Lead with the outcome the user wants ("Track unlimited habits", "Remove all ads"), not a feature checklist or the price. Show the transformation.
- Concrete benefits, not feature names. "Sync across all your devices" beats "iCloud integration." 3–5 benefits, scannable, each with an icon.
- Plan selection. If offering multiple durations, anchor: show annual next to monthly with a "Save 40%" / "Best value" badge so the annual looks like the smart default. Pre-select the plan you want most users to pick.
- Trial framing (if used): "Start 7-day free trial" as the primary CTA reduces friction far more than "Subscribe." Be explicit about what happens after.
- Social proof (optional): ratings count, testimonials, or "Join 50,000 users" — only if true.
- One primary CTA. A single, high-contrast button. Secondary actions (other plan, restore, close) are visually quieter.
- Required legal row at the bottom: price recap, Restore, Terms, Privacy.
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.
- 4d ago First seen · 76 lines · 124 tokens per session scan A b09dc3478a31
paywall-design is a skill published in the GitHub repository markdavidgan/apple-dev-skills (5 stars, last pushed 9d ago), licensed MIT. It adds 124 tokens to every session and 1,167 once invoked, about $0.0006 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-09-03.
Other skills, from other repositories
asc-ppp-pricing
Set territory-specific pricing for subscriptions and in-app purchases using current asc setup, pricing summary, price import, and price schedule commands. Use when adjusting prices by country or implementing localized PPP strategies.
asc-revenuecat-catalog-sync
Reconcile App Store Connect subscriptions and in-app purchases with RevenueCat products, entitlements, offerings, and packages using asc and RevenueCat MCP. Use when setting up or syncing subscription catalogs across ASC and RevenueCat.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
forms-inputs-checkout
Use when designing, critiquing, or implementing forms, inputs, validation, checkout, registration, payment, or any data-entry flow.
app-store-screenshots
Use when building App Store or Google Play screenshot pages, generating exportable marketing screenshots for iOS and/or Android apps, or scaffolding a screenshot editor with Next.js. Triggers on app store, play store, screenshots, marketing assets, html-to-image, phone mockup, android screenshots, feature graphic.
asc-apple-ads
Use when managing Apple Ads with asc, including OAuth profiles, ad-account discovery, Platform API v1 campaigns and targeting, reports, assets, recommendations, guarded mutations, raw requests, and Campaign Management API v5 migration.