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 setupgit 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/setup)<a href="https://agentmods.dev/skills/revenuecat/play-billing-skills/setup"><img src="https://agentmods.dev/badge/skills/revenuecat/play-billing-skills/setup/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/setup"><img src="https://agentmods.dev/badge/skills/revenuecat/play-billing-skills/setup.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.00056 | $0.02744 |
| Opus 5 | $0.00028 | $0.01372 |
| Sonnet 5 | $0.00011 | $0.00549 |
| Haiku 4.5 | $0.00006 | $0.00274 |
Grade A, and why
setup 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase 0: Intent
Use this skill when any of the following is true:
- You are starting a new Android billing integration and have not yet configured Play Console, products, API access, or RTDN.
- A teammate asks you to "set up Play billing" or "wire up server side purchase notifications" before any code lands.
- You hit errors like "This version of the app is not configured for billing through Google Play", 403 responses from the Google Play Developer API, or missing Pub/Sub test notifications, and you need to retrace the environment setup.
Outcome: a verified environment with a Play Developer account, a linked Payments profile, an internal test track build, at least one active product, a service account with the right Play Console roles, and a Pub/Sub topic receiving Real Time Developer Notifications.
Phase 1: Discovery
Gather facts before changing anything. Ask or check:
- Does the developer account already exist, and is it individual or organization? Organization verification can take up to two weeks.
- Is there a verified Google Payments Center profile? Without it, you cannot create paid products or publish in app purchases.
- What is the app's package name, signing configuration, and current Play Console upload state (any track)?
- Which GCP project is linked to the Play Console app? RTDN and the Play Developer API both depend on this link.
- Does a service account already exist for this backend, and which roles are granted in the Play Console (not only in GCP IAM)?
- Is there an existing Pub/Sub topic, and has
[email protected]been granted Publisher on it? - Will the server side consumer use a push subscription (public HTTPS endpoint) or a pull subscription (firewalled or batched)?
If any answer is "unknown," treat it as a discovery task before executing Phase 3.
Phase 2: Plan
Work top down. Each step unblocks the next, so do not skip ahead.
- Register and verify the Google Play Developer Account; pay the one time $25 fee.
- Create and verify the Google Payments Center profile and tax information.
- Add the Play Billing Library 9.x dependency and upload a signed build to the internal test track.
- Create at least one product (one time product or subscription) and activate it.
- Link a GCP project to the Play Console app, create a service account, and grant minimum Play Console roles.
- Create a Pub/Sub topic, grant Google publish access, and create a push or pull subscription.
- Point Play Console RTDN at the full topic name and send a test notification.
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 · 233 lines · 56 tokens per session scan A 5997352891c7
setup is a skill published in the GitHub repository RevenueCat/play-billing-skills (53 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 2,744 once invoked, about $0.0003 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
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.