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/ai-toolkit --skill revenuecat-store-stategit clone --depth 1 https://github.com/RevenueCat/ai-toolkitWrote 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/ai-toolkit/revenuecat-store-state)<a href="https://agentmods.dev/skills/revenuecat/ai-toolkit/revenuecat-store-state"><img src="https://agentmods.dev/badge/skills/revenuecat/ai-toolkit/revenuecat-store-state/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/ai-toolkit/revenuecat-store-state"><img src="https://agentmods.dev/badge/skills/revenuecat/ai-toolkit/revenuecat-store-state.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.00043 | $0.00794 |
| Opus 5 | $0.00022 | $0.00397 |
| Sonnet 5 | $0.00009 | $0.00159 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
revenuecat-store-state 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.
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing product store state
The RevenueCat MCP store-state tools read and write product state — status, pricing, availability, and review metadata — directly in App Store Connect and Google Play Console. Reads are immediate; writes are asynchronous operations that must be polled for completion.
The same operations are available via the rc CLI (see the revenuecat-cli skill), but the CLI uses an auditable plan/apply model instead of the MCP read-then-poll model:
rc products show <product-id> --store-statereads a product's current live store state (the closest CLI equivalent ofget-product-store-state).rc products store plan <app-id> --file <csv|json>computes a reviewable diff and returns a plan ID;rc products store show <plan-id>re-displays a saved plan.rc products store apply <plan-id>applies that plan (orrc products store discard <plan-id>). Apply handles the async operation internally, so there is no separate poll step.rc products prices setsets prices;rc products store screenshot <product-id>uploads a review screenshot.
Confirm exact flags with rc commands --schemas --json.
Refer to the MCP tool schemas for the exact parameters of each tool.
Prerequisites
Store-state writes require store credentials connected to the RevenueCat project (an App Store Connect API key, or a Google Play service account with the Manage store presence permission) and a RevenueCat login with write access to the project. If a write fails with a credentials or permission error, report what is missing and how to fix it (dashboard app settings for store credentials) instead of retrying.
Confirm before writing
Store-state writes go straight to production stores and can change what live customers see and pay. Before any of the following, show the user a compact before → after summary of the exact change (based on a fresh get-product-store-state read) and proceed only after they explicitly confirm:
- Price changes on a live product
- Removing availability or territories
- Submitting products for store review
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 · 45 lines · 43 tokens per session scan A 5982ec8a006a
revenuecat-store-state is a skill published in the GitHub repository RevenueCat/ai-toolkit (65 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 794 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-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.