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 PollyGlot/google-play-cli-skills --skill gplay-appstoregit clone --depth 1 https://github.com/PollyGlot/google-play-cli-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/pollyglot/google-play-cli-skills/gplay-appstore)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-appstore"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-appstore/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/pollyglot/google-play-cli-skills/gplay-appstore"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-appstore.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.00059 | $0.01213 |
| Opus 5 | $0.00030 | $0.00607 |
| Sonnet 5 | $0.00012 | $0.00243 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
gplay-appstore 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 10d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay appstore (alternative app store operations)
gplay appstore acts for the operator of a third-party Android app store:
the catalog that store mirrors from Play, and the apps it hosts and must send to
Google for review. Publishing your own app to Google Play is gplay-release-flow.
Shared conventions (auth, output, exit codes, --dry-run/--confirm, the
[experimental] contract) are in gplay-cli-usage. Read the current flags from
gplay appstore <command> --help: it is long and complete, and this skill
carries the order the commands go in and the traps between them.
Caller and subject: two packages, one command
| Flag | Role | Falls back to |
|---|---|---|
--store-package |
the caller, your app store's own package | $GPLAY_APP_STORE_PACKAGE (ADR-0043) |
--package |
the subject, the hosted app acted on | the repo's .gplay/config.json pin |
Swapping the two is the standard failure here. The catalog reads take the
caller only, and address the Play app as a positional argument: they ignore
the repo pin, so a resolved .gplay/config.json still leaves --store-package
required. A missing caller is a usage error (exit 2) before any HTTP call.
A 403 (exit 11) on any of these commands means the caller is not enrolled for alternative distribution; the message names the enrollment.
Mirror Play's catalog
gplay appstore catalog view com.example.app --store-package com.mystore.app
gplay appstore catalog events list \
--start-time 2026-07-01T00:00:00Z --end-time 2026-07-08T00:00:00Z
catalog events list is the incremental sync feed, and the reason to script
this surface at all: each event is a MODIFICATION (re-fetch that app with
catalog view) or a DELETION (delist it). Persist each run's --end-time and
feed it back as the next run's --start-time; both bounds are required, the
range is [start, end), and an end at or before the start is exit 2.
Pagination is one page per invocation, and the page token is only valid against
identical parameters: carry --start-time, --end-time and --page-size
unchanged into every follow-up call with --page-token. In table output the
next token arrives on stderr, in --output json as nextPageToken.
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.
- 10d ago First seen · 97 lines · 59 tokens per session scan A 7c9988e3e515
gplay-appstore is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 59 tokens to every session and 1,213 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-31.
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.