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-setupgit 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-setup)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-setup"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-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/pollyglot/google-play-cli-skills/gplay-setup"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-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.00061 | $0.00591 |
| Opus 5 | $0.00030 | $0.00296 |
| Sonnet 5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
gplay-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 8d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay setup (auth onboarding)
Get gplay talking to the Google Play Developer API. This skill covers the
auth namespace end to end; for the conventions every command shares
(credential resolution order, exit codes, output), see gplay-cli-usage.
The credential
gplay authenticates as a Google Cloud service account with the
Android Publisher role, invited to your Play Console. You supply its JSON
key one of three ways (resolution order in gplay-cli-usage):
GPLAY_SERVICE_ACCOUNT, a path to the JSON file or the inline JSON itself (handy for CI secrets).--service-account <path-or-json>on any command, overrides the env.- A stored Account registered with
gplay auth login(the credential lands in the OS keystore, seegplay auth statusfor where).
First-run flow
# 1. Register the service account as the active Account.
gplay auth login --service-account ./service_account.json
# 2. Confirm what gplay will use, and where the credential lives.
gplay auth status
# 3. Run ordered diagnostics (credential valid? scopes? developer id?).
gplay auth doctor
auth status prints the active Account, the keystore backend, and the
credential's location. auth doctor runs ordered checks and is the first
thing to reach for when an authenticated command fails; it pinpoints whether
the problem is a bad key (exit 10) or a service account that is valid but
not invited on the app/account (exit 11).
Managing stored accounts
gplay auth list # every registered Account
gplay auth logout <name> --confirm # remove an Account from the config + keystore
auth logout removes a stored credential, so it is --confirm-gated like
every destructive write (missing → exit 3, naming the flag).
Use --account <name> on later commands to target a specific stored Account
when you have more than one.
Verify, then hand off
Once gplay auth doctor is green, auth is done. Every other skill assumes the
credential set up here; the next step is gplay-apps, to register a package
(gplay apps add <package>) and pin it to the repo (gplay init).
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.
- 8d ago First seen · 61 lines · 61 tokens per session scan A 7ff16bd74e2b
gplay-setup is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 591 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
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.