creating-paywall

creating-paywall is a skill for Claude Code from SwiftfulThinking/SwiftfulStarterProject. It costs 91 tokens per session (1,959 once invoked), scanned A, original, MIT.

A coding workflow for adding a new subscription or purchase screen variant to an iOS app. It creates the view and connects it to the app's A/B test switch, with support for custom, Apple's StoreKit, and RevenueCat paywalls.

In plain words
What is it for?
Use it when building a new paywall, subscription screen, or purchase-flow variant in a Swift app.
Why use it?
It removes the repeated setup work needed to make a new paywall appear in the existing purchase system. It also keeps the new variant connected to the app's established purchase and test structure.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it when building a new paywall, subscription screen, or purchase-flow variant in a Swift app.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swiftfulthinking/swiftfulstarterproject/creating-paywall
Install

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.

Any agent
npx skills add SwiftfulThinking/SwiftfulStarterProject --skill creating-paywall
Clone the repo
git clone --depth 1 https://github.com/SwiftfulThinking/SwiftfulStarterProject

Made for: Claude Code.

Wrote 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.

agentmods badge for creating-paywall

README.md
[![agentmods](https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-paywall.svg)](https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-paywall)
Your own site
<a href="https://agentmods.dev/skills/swiftfulthinking/swiftfulstarterproject/creating-paywall"><img src="https://agentmods.dev/badge/skills/swiftfulthinking/swiftfulstarterproject/creating-paywall.svg" alt="Measured on agentmods" height="20"></a>
Per session 91 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,959 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00091 $0.01959
Opus 5 $0.00046 $0.00979
Sonnet 5 $0.00018 $0.00392
Haiku 4.5 $0.00009 $0.00196

Measured 2d ago against content hash ca65ca32a85e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

creating-paywall 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 2d 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.

.claude/skills/creating-paywall/SKILL.md · 261 lines

How it starts

The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Creating Paywall

Add a new paywall variant view and wire it into the paywall AB test.

Architecture

The paywall system has two layers:

  1. Paywall screen (VIPER) — Core/Paywall/ — already exists, handles products loading, purchase logic, analytics, routing
  2. Paywall variant viewsCore/Paywall/Paywalls/ — pure UI components that receive data via closures

PaywallView.swift switches on the AB test to render the active variant. New paywalls are added as variant views, not new screens.

Steps

  1. Determine the variant name (PascalCase, e.g., MinimalPaywall, FeatureListPaywall)
  2. Determine the variant type (custom, storeKit, or revenueCat)
  3. Create the variant view file in Core/Paywall/Paywalls/
  4. Add a case to PaywallTestOption enum
  5. Wire the variant into PaywallView.swift switch statement
  6. Add preview(s) for the new variant

Variant Types

Type When Products UI Owner
Custom (most common) Full control over layout and design Loaded via presenter, passed as [AnyProduct] You build it
StoreKit Apple's native SubscriptionStoreView Loaded by StoreKit from product IDs Apple's UI
RevenueCat RevenueCat's remote paywall UI Managed by RevenueCat dashboard RevenueCat SDK

Custom Paywall Template

Custom paywalls are the most common type. They receive products and closures from PaywallView:

import SwiftUI

struct {VariantName}PaywallView: View {

    var products: [AnyProduct] = []
    var onBackButtonPressed: () -> Void = { }
    var onRestorePurchasePressed: () -> Void = { }
    var onPurchaseProductPressed: (AnyProduct) -> Void = { _ in }

    var body: some View {
        ZStack {
            // Background
            Color.blue.ignoresSafeArea()

            VStack(spacing: 0) {
                // Header / marketing content
                // ...

                // Product list
                ForEach(products) { product in
                    // product.title, product.priceStringWithDuration, product.subtitle
                }

                // CTA button (if single product) or tap on product row

                // REQUIRED: Restore purchase link
                Text("Restore Purchase")
                    .underline()
                    .asButton {
                        onRestorePurchasePressed()
                    }

                // REQUIRED: Legal links
                HStack {
                    Link("Privacy Policy", destination: URL(string: Constants.privacyPolicyURL)!)
                    Text("|")
                    Link("Terms of Service", destination: URL(string: Constants.termsOfServiceURL)!)
                }
                .font(.caption2)
                .foregroundStyle(.secondary)
            }
        }
        .overlay(
            Image(systemName: "xmark.circle.fill")
                .font(.title)
                .padding(8)
                .tappableBackground()
                .asButton {
                    onBackButtonPressed()
                }
                .padding(16),
            alignment: .topLeading
        )
    }
}

#Preview {
    {VariantName}PaywallView(products: AnyProduct.mocks)
}

Read the full file on GitHub · 261 lines

Changes

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.

  1. 2d ago First seen · 261 lines · 91 tokens per session scan A ca65ca32a85e

Subscribe to this mod's changes

creating-paywall is a skill published in the GitHub repository SwiftfulThinking/SwiftfulStarterProject (74 stars, last pushed 5mo ago), licensed MIT. It adds 91 tokens to every session and 1,959 once invoked, about $0.0005 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-04.

Related

Other skills, from other repositories

play-billing-library-version-upgrade

Use this skill when upgrading or migrating an Android project from any legacy Google Play Billing Library (PBL) version to the latest stable version of PBL.

android/skills · 39 tokens

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.

rorkai/app-store-connect-cli-skills · 51 tokens

axiom-implement-iap

Use when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.

CharlesWiltgen/Axiom · 29 tokens

google-play

Google Play Developer API (Android Publisher) integration with managed OAuth. Manage apps, subscriptions, in-app purchases, and reviews. Use this skill when users want to interact with Google Play Console programmatically. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway).

CraftOS-dev/CraftBot · 70 tokens

subscription-lifecycle

Generates StoreKit 2 subscription lifecycle management — grace periods, billing retry, offer codes, win-back offers, upgrade/downgrade paths, and subscription status monitoring. Use when user needs post-purchase subscription state handling beyond the initial paywall.

rshankras/claude-code-apple-skills · 55 tokens

subscription-offers

Generates StoreKit 2 code for all subscription offer types — introductory, promotional, offer codes, and win-back. Includes eligibility checks, offer presentation, and the preferredSubscriptionOffer modifier. Use when adding subscription offers, free trials, or promotional pricing.

rshankras/claude-code-apple-skills · 55 tokens