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-tracksgit 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-tracks)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-tracks"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-tracks/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-tracks"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-tracks.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.00052 | $0.00742 |
| Opus 5 | $0.00026 | $0.00371 |
| Sonnet 5 | $0.00010 | $0.00148 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
gplay-tracks 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay tracks (+ availability + testers)
Tracks are where releases live; testers are who may install a closed track.
gplay folds the two together because they are operationally coupled
(DESIGN §10). Shared conventions (auth, --package, output, exit codes) are
in gplay-cli-usage; shipping builds onto tracks is gplay-release-flow.
Inspect tracks
gplay tracks list --package com.example.app # every track on the app
gplay tracks view --track production # one track's full state
tracks view answers "is anything wrong on this track right now?": the latest
release, its status, and rollout fraction.
Create a closed track
gplay tracks create qa-team
The create endpoint supports exactly one kind: a CLOSED_TESTING track on
the DEFAULT (phone) form factor, so there is no --type / --form-factor
flag, and there is no API path to create open/internal tracks (those exist
already). Creating a track that already exists surfaces the API error (exit
30); gplay does not fake idempotency. Use --dry-run to preview the
TrackConfig; there is no --confirm (a closed test track is low-stakes).
This is the other half of the release-flow trackhint: an
upload/promoteto a custom closed track that doesn't exist yet fails with exit30and tells you to rungplay tracks create <name>first; gplay never auto-creates a track as a side effect. Seegplay-release-flow.
Country availability (read-only)
gplay tracks availability view --track production
Availability, which countries a track's artifacts ship to, is read-only
at the Developer API level (ADR-0012): there is no writer. To change where an
app is available, use the Play Console. The bare gplay tracks availability
prints help; the read is availability view.
Testers (closed-track audience)
gplay testers list --track qa-team
gplay testers set --track qa-team --group [email protected],[email protected]
gplay testers set --track qa-team --clear # close the closed test
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 · 74 lines · 52 tokens per session scan A 49e8773d2653
gplay-tracks is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 742 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.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
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"…