in-app-purchases

in-app-purchases is a skill for Claude Code from launch52-ai/flutter-template. It costs 45 tokens per session (1,541 once invoked), scanned A, original, MIT.

A Flutter setup for selling subscriptions or one-time digital purchases through RevenueCat. It includes product access levels, paywalls, purchase restoration, and subscription status.

In plain words
What is it for?
Use it for subscriptions, one-time purchases, premium features, paywalls, and restoring purchases.
Why use it?
It organizes purchase and subscription behavior across app platforms, including checking what access a customer has after buying.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Good fit Use it for subscriptions, one-time purchases, premium features, paywalls, and restoring purchases.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/launch52-ai/flutter-template/in-app-purchases
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 launch52-ai/flutter-template --skill in-app-purchases
Clone the repo
git clone --depth 1 https://github.com/launch52-ai/flutter-template

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 in-app-purchases

README.md
[![agentmods](https://agentmods.dev/badge/skills/launch52-ai/flutter-template/in-app-purchases.svg)](https://agentmods.dev/skills/launch52-ai/flutter-template/in-app-purchases)
Your own site
<a href="https://agentmods.dev/skills/launch52-ai/flutter-template/in-app-purchases"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/in-app-purchases.svg" alt="Measured on agentmods" height="20"></a>
Per session 45 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,541 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.00045 $0.01541
Opus 5 $0.00023 $0.00771
Sonnet 5 $0.00009 $0.00308
Haiku 4.5 $0.00005 $0.00154

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

Security

Grade A, and why

in-app-purchases 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.

.claude/skills/in-app-purchases/SKILL.md · 189 lines

How it starts

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

In-App Purchases & Subscriptions

Monetize your Flutter app with RevenueCat - the industry-standard solution for in-app purchases and subscriptions. Handles cross-platform billing, receipt validation, and subscription management.

When to Use This Skill

  • Adding subscriptions or one-time purchases
  • Implementing a paywall
  • Managing premium features/entitlements
  • Restoring purchases
  • User asks "add subscription", "paywall", "in-app purchase", "monetize", or "RevenueCat"

Questions to Ask

  1. Purchase types: Subscriptions, one-time purchases, or both?
  2. Subscription tiers: Free, premium only, or multiple tiers (basic/pro/enterprise)?
  3. Trial period: Offer free trial? How long?
  4. Paywall trigger: Where should the paywall appear? (feature-gated, onboarding, settings)
  5. Restore flow: Where should users restore purchases? (settings, paywall)

Quick Reference

RevenueCat Concepts

Concept Description
Offering Container for products shown to users (e.g., "default", "sale")
Package Specific product in an offering (e.g., "monthly", "annual")
Entitlement Access level granted by purchase (e.g., "premium", "pro")
CustomerInfo User's purchase state, active entitlements, subscriptions

Product Types

Type Use Case Example
Auto-renewable Recurring access Monthly/annual subscription
Non-consumable Permanent unlock Remove ads, lifetime access
Consumable One-time use Credits, coins

Reference Files

  • reference/services/purchases_service.dart - RevenueCat wrapper
  • reference/repositories/ - Domain interface + implementation
  • reference/providers/purchases_providers.dart - Riverpod state
  • reference/failures/purchases_failures.dart - Sealed failures
  • reference/models/subscription_status.dart - Freezed models

Workflow

Phase 1: RevenueCat Setup

  1. Create RevenueCat account at revenuecat.com
  2. Create a new project in RevenueCat dashboard
  3. Add App Store Connect and Play Console credentials
  4. Create products in App Store Connect / Google Play Console
  5. Configure products in RevenueCat → Products
  6. Create Entitlements (e.g., "premium")
  7. Create Offerings and add Packages

Read the full file on GitHub · 189 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. 7d ago First seen · 189 lines · 45 tokens per session scan A 73adae65a3d8

Subscribe to this mod's changes

in-app-purchases is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 45 tokens to every session and 1,541 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-31.

Related

Other skills, from other repositories

integrating-revenuecat

Integrates RevenueCat in-app purchases and subscriptions into Flutter apps using purchasesflutter (v10.x). Use when implementing paywalls, checking entitlements via CustomerInfo, configuring PurchasesConfiguration for iOS or Android, displaying paywalls with purchasesuiflutter, handling purchase errors via…

Poorgramer-Zack/dart-expert-skills · 111 tokens

stripe-best-practices

Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial accounts, integration surfaces (Checkout, Payment Element), migrating from deprecated Stripe APIs, and security best…

ever-works/directory-web-template · 111 tokens

merge-seed

Merge upstream React Starter Kit updates (the seed remote) into main, preserving this project's identity, scope, and behavior. Use when asked to sync, pull, or merge the seed / starter kit / upstream template.

kriasoft/react-starter-kit · 49 tokens

firebase-messaging

Use when setting up Firebase Cloud Messaging, managing permissions and tokens, handling background/foreground notification taps, or dispatching messages server-side (HTTP v1).

evanca/flutter-ai-rules · 35 tokens

firebase-app-check

Use when implementing app attestation, configuring App Check providers, setting up debug tokens, enabling backend enforcement, or managing token refresh.

evanca/flutter-ai-rules · 30 tokens

flutter-app-architecture

Use when scaffolding a project, refactoring into layers, creating view models/repositories, configuring dependency injection, or implementing unidirectional data flow (MVVM).

evanca/flutter-ai-rules · 38 tokens