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 RevenueCat/play-billing-skills --skill configuring-the-sdkgit clone --depth 1 https://github.com/RevenueCat/play-billing-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/revenuecat/play-billing-skills/configuring-the-sdk)<a href="https://agentmods.dev/skills/revenuecat/play-billing-skills/configuring-the-sdk"><img src="https://agentmods.dev/badge/skills/revenuecat/play-billing-skills/configuring-the-sdk/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/revenuecat/play-billing-skills/configuring-the-sdk"><img src="https://agentmods.dev/badge/skills/revenuecat/play-billing-skills/configuring-the-sdk.svg" alt="Reviewed on agentmods" width="80" 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.00053 | $0.01383 |
| Opus 5 | $0.00026 | $0.00691 |
| Sonnet 5 | $0.00011 | $0.00277 |
| Haiku 4.5 | $0.00005 | $0.00138 |
Grade A, and why
configuring-the-sdk 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 12d 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.
This is a copy
95% identical to rc-configuring-the-sdk — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring the RevenueCat Android SDK
Use this skill to add and configure RevenueCat (purchases-kt) in an Android app. A single Purchases.configure call replaces BillingClient setup, connection lifecycle management, reconnection handling, and launch-time purchase queries.
Work through the phases in order. The full chapter on revenuecat.com has the complete reference text.
Phase 1: Discovery
Find out whether RevenueCat is already wired up and where billing code currently lives.
-
Search for an existing configure call and prior SDK version.
rg -n "Purchases\.configure|PurchasesConfiguration" --type kotlin --type java rg -n "com\.revenuecat\.purchases" -g '*.gradle*' -g '*.toml' -
Search for the existing billing surface you may be replacing.
rg -n "BillingClient|PurchasesUpdatedListener|startConnection" --type kotlin --type java -
Record answers before moving on.
| Question | Where to look |
|---|---|
Is Purchases.configure already called? |
App startup, Application.onCreate, main Activity.onCreate |
| Which module owns billing today? | app/build.gradle(.kts), any :billing module |
| Is there an auth system with a stable user id? | Login flow, session store |
| Debug vs release build detection available? | BuildConfig.DEBUG |
If Purchases.configure already runs, stop and confirm with the user before changing it. Configuration runs once per process.
Phase 2: Plan
Decide three things before writing code.
2.1 Where to call configure
| Location | When to choose |
|---|---|
Application.onCreate |
Default. Ensures the SDK is ready before any Activity or background work touches purchases. |
First Activity.onCreate |
Only if the app has no custom Application class and you are not willing to add one. |
Call configure exactly once per process. Calling it from an Activity risks re-running it on configuration changes if you are not careful; the Application path avoids that.
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.
- 12d ago First seen · 151 lines · 53 tokens per session scan A 50cb94355f02
configuring-the-sdk is a skill published in the GitHub repository RevenueCat/play-billing-skills (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 53 tokens to every session and 1,383 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to rc-configuring-the-sdk, differing in 2 lines, and is treated as a copy.
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.
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.
axiom-implement-iap
Use when the user wants to add in-app purchases, implement StoreKit 2, or set up subscriptions.
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).
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.
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.