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 hanamizuki/solopreneur --skill gplay-iap-setupgit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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/hanamizuki/solopreneur/gplay-iap-setup)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/gplay-iap-setup"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/gplay-iap-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/hanamizuki/solopreneur/gplay-iap-setup"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/gplay-iap-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.04120 |
| Opus 5.5 | $0.00020 | $0.01648 |
| Sonnet 5.5 | $0.00010 | $0.00824 |
| Haiku 4.5 | $0.00005 | $0.00412 |
Grade A, and why
gplay-iap-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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gplay-iap-setup — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 525 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In-App Purchase Setup for Google Play
Use this skill when you need to set up monetization for your Android app.
Two APIs: Legacy vs New Monetization
Google Play has two APIs for one-time products:
Legacy (gplay iap) |
New Monetization (gplay onetimeproducts) |
|
|---|---|---|
| API | inappproducts |
monetization.onetimeproducts |
| Price format | priceMicros/currency |
units/nanos/currencyCode |
| Structure | Flat prices map |
purchaseOptions with regionalPricingAndAvailabilityConfigs |
| States | active/inactive |
DRAFT → ACTIVE (requires explicit activation) |
| Regional pricing | --auto-convert-prices flag |
--regions-version required |
Prefer the new monetization API (gplay onetimeproducts) for new products. It supports purchase options, better regional pricing control, and is the actively developed API.
Use the legacy API (gplay iap) only for managing existing legacy products.
Never mix the two APIs for the same product. A product created via gplay iap create cannot be managed via gplay onetimeproducts and vice versa.
Critical: Product IDs Are Permanent
Google Play permanently reserves product IDs after deletion. If you create premium_unlock and later delete it, the ID premium_unlock can never be reused — not even with a different API. Choose product IDs carefully.
This means:
- Do NOT create a "test" product with a good ID and then delete it
- Do NOT create via the legacy API and then try to recreate via the new API
- If you burn an ID, you must choose a new one (e.g.,
premium_unlock_v2)
One-Time Products (New Monetization API)
List products
gplay onetimeproducts list --package com.example.app
Create product
--regions-version is required — the create command uses PATCH with allowMissing=true internally:
gplay onetimeproducts create \
--package com.example.app \
--product-id premium_unlock \
--json @product.json \
--regions-version "2025/03"
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 525 lines · 51 tokens per session scan A 057067f51999
gplay-iap-setup is a skill published in the GitHub repository hanamizuki/solopreneur (156 stars, last pushed 14d ago), licensed MIT. It adds 51 tokens to every session and 4,120 once invoked, about $0.0002 per session on Opus 5.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).
rc-revenuecat-api-quick-reference
Use this skill as a quick reference for the RevenueCat Android SDK 10.x and REST API. Covers SDK init, common Purchases calls, CustomerInfo / Offerings access patterns, and the most used REST endpoints.
rc-catalog-management
Use this skill when managing the Android product catalog through the Play Console and the RevenueCat dashboard. Covers the two sided catalog flow (create in Play Console, import or map in RevenueCat), entitlement and offering maintenance, and why you do not call the Google Play Developer API directly.