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.00051 | $0.00826 |
| Opus 5.5 | $0.00020 | $0.00330 |
| Sonnet 5.5 | $0.00010 | $0.00165 |
| Haiku 4.5 | $0.00005 | $0.00083 |
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 29d 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 — 73 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 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.
Mirror Play's catalog
gplay appstore catalog view com.example.app --store-package com.mystore.app
gplay appstore catalog events list \
--since 2026-07-01T00:00:00Z --until 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 --until and
feed it back as the next run's --since.
Take a hosted app through review
The four writes are an ordered path: Google refuses everything else for an app until its record exists.
# 1. Once per hosted app: the record.
gplay appstore create --package com.example.app --store-package com.mystore.app
# 2. Upload each artifact; the printed id is the point of the call.
gplay appstore apk upload ./base.apk --package com.example.app # → apkId
gplay appstore image upload ./icon.png --package com.example.app # → imageId
gplay appstore policy upload ./privacy.pdf --package com.example.app # → fileId
# 3. Assemble those ids into one JSON body and submit to review.
gplay appstore submit --file ./hosted-app.json --dry-run # rehearse, zero HTTP
gplay appstore submit --file ./hosted-app.json --confirm # irrevocable
# 4. Later, to withdraw the app from the store, or put it back:
gplay appstore publish-status set unpublished --package com.example.app
gplay appstore publish-status set published --package com.example.app
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.
- 29d ago Changed 278660a56d77
- 1mo ago Changed · -24 lines · -8 tokens per session eb01ce91a22c
- 1mo 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 51 tokens to every session and 826 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-31.
Other skills, from other repositories
gps-monetization
Inspect and manage Google Play subscriptions, one-time products, offers, and legacy IAPs with gps. Use for product catalogs, base plans, offers, or regional price conversion — not purchase-token refunds (see gps-purchases).
app-paywall-pilot
Design, audit, debug, and implement App Store-compliant mobile paywalls, subscription flows, pricing screens, trials, offers, feature gates, and subscription lifecycle UX. Use when the user asks to audit my paywall, fix App Store 3.1.2 rejection, improve trial-to-paid, choose plans/prices/trials, review…
onesub
Use this skill when the user wants to add in-app purchases (subscriptions, consumables, or non-consumables) to a React Native / Expo mobile app. onesub is the open-source server side of react-native-iap — one line of Express middleware validates Apple StoreKit 2 and Google Play Billing receipts. Pair it with the…
user-journey-tracking
Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.
compose-ui-builder
Open and edit checked-in .uid designs, compare real renders against references, and implement them in application code. Author and edit a Compose UI design over MCP against a compose-preview serve deployment — create a screen or a Wear widget, insert and edit nodes, and export the Kotlin, PNG or SVG. Also use when no…
storekit
In-app purchases and subscriptions on iOS/iPadOS/macOS with StoreKit 2 (iOS 26 era) — fetch products with Product.products(for:), buy with Product.purchase and switch on PurchaseResult (.success/.pending/.userCancelled), always unwrap VerificationResult (.verified/.unverified), gate access from…