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-reportsgit 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-reports)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-reports"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-reports/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-reports"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-reports.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.00077 | $0.01002 |
| Opus 5.5 | $0.00031 | $0.00401 |
| Sonnet 5.5 | $0.00015 | $0.00200 |
| Haiku 4.5 | $0.00008 | $0.00100 |
Grade A, and why
gplay-reports 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 9d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay reports (monthly Bulk reports)
gplay reports reads the CSV exports Play deposits every month in the
developer account's Reporting bucket on Cloud Storage. It is the only
programmatic source for installs, uninstalls, ratings over time, Store listing
acquisition and revenue. Shared conventions are in gplay-cli-usage.
The whole group is [experimental]: pin an exact gplay release before a CI
job depends on its flags or output.
Pick the right source
| Question | Command |
|---|---|
| Installs, uninstalls, active devices | gplay reports installs |
| Average rating over time | gplay reports ratings |
| Crash and ANR counts per month | gplay reports crashes |
| Store listing visitors and conversions | gplay reports store-performance |
| One subscription's subscribers and churn | gplay reports subscription-stats --product <id> |
| What Google paid out (charges, fees, taxes, refunds) | gplay reports earnings |
| Orders as they happen (estimates, low latency) | gplay reports sales |
Crash and ANR rates after a rollout, day by day, belong to gplay vitals
(gplay-vitals), not here. Reviews older than 7 days are gplay reviews history (gplay-reviews), which reads the same bucket.
Start with the inventory
gplay reports list
gplay reports list --family installs --package com.example.app --since 2026-01
It shows which families, months, dimensions and subscription product ids the
bucket holds. Read it before choosing --month, --dimension or --product
instead of guessing them: a dimension the bucket lacks fails with exit 2,
and the message lists the ones present.
Read one family
gplay reports installs --month 2026-09 --dimension country
gplay reports store-performance --dimension traffic_source
gplay reports earnings --month 2026-09 --package com.example.app
gplay reports installs --since 2026-01 --until 2026-06 --dimension country --output json
- Without
--month, the latest month present is read. --since/--untilmerge a range into one result set; a missing month is skipped with a stderr warning, so check thereportobject for the months actually read.earningsandsalescover every app of the account:--packagefilters their rows, and the Project pin does not apply to them.
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.
- 9d ago First seen · 87 lines · 77 tokens per session scan A efe06fd0fce0
gplay-reports is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 1,002 once invoked, about $0.0003 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-10-14.
Other skills, from other repositories
flake-triage
Decide whether a preview the visual-diff bot flagged actually regressed or is simply nondeterministic, using a repeat-render oracle at a single commit. Use when a PR's preview diff reports a changed preview whose source the PR does not touch, or when a render, GIF or filmstrip is suspected of being unstable.
render-evidence
Capture the before/after rendered PNGs a UI-affecting PR in this repository needs as visual evidence, including bringing an Android SDK up in a fresh sandbox. Use when a change touches a Compose @Preview, a catalog, the VS Code webview, an overlay, a theme, an icon or a fixture, and the PR body needs real pixels.
steward
Drive a pull request on this repository to green — which fast checks to run before pushing, how to read a red check, and what to do about a review comment. Use when a CI failure, a review comment, a merge conflict, or a scheduled check-in arrives on a PR you opened or were asked to drive.
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…
compose-design-catalog
Generate an importable design-artifact sticker sheet for a whole Compose component system (Compose M3, Wear Compose M3, Glimmer, Glance/Wear widgets). Use when you want a code-derived component catalog — each component in its primary modes, in two variants (ideal render + bordered layout), with extracted design tokens…
compose-preview-ci
Set up or repair GitHub Actions CI that renders Compose @Preview composables and posts before/after diff comments on pull requests. Use when wiring preview diffs into a repo for the first time, when preview comments don't appear on fork PRs (the two-stage render/publish split), when migrating off the legacy…