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-vitalsgit 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-vitals)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-vitals"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-vitals/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-vitals"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-vitals.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.00076 | $0.01468 |
| Opus 5 | $0.00038 | $0.00734 |
| Sonnet 5 | $0.00015 | $0.00294 |
| Haiku 4.5 | $0.00008 | $0.00147 |
Grade A, and why
gplay-vitals 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 6d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay vitals (post-launch quality signals)
gplay vitals reads Android vitals, the post-launch quality signals you
know from the Play Console: crash rate, ANR rate, slow cold start, slow
rendering, excessive wakeups, low-memory kills, stuck background wakelocks, plus
error reports and Play-detected anomalies. Shared conventions (auth, output,
exit codes, --package pinning) are in gplay-cli-usage.
Two things make this namespace different from the rest of gplay:
- A distinct Google service. Vitals is backed by the Play Developer
Reporting API (
playdeveloperreporting), not the Android Publisher API. Same service-account file, but a different OAuth scope (…/auth/playdeveloperreporting). If the service account was invited only for publishing, vitals calls fail with a 403 (exit11) until the reporting scope is granted; that is an environment fix, not a flag. - Read-only, always. Every
vitalscommand only reads metrics. There is no write here, soGPLAY_READONLYnever blocks it, and no command needs--confirm.
Preset rate commands: the fast path
Each vital has an opinionated preset that needs no metric/dimension knowledge; it reports the set's primary metric over a default 28-day DAILY window:
gplay vitals crashes # crash rate (on the pinned package)
gplay vitals anr # ANR rate
gplay vitals slowstart # slow cold-start rate
gplay vitals slowrendering # janky-frames rate
gplay vitals excessivewakeup # excessive wakeup rate
gplay vitals lmk # low-memory-kill rate
gplay vitals stuckbgwakelock # stuck background wakelock rate
All the presets share the same knobs:
gplay vitals crashes --by versionCode --version 123 # slice, then filter to one build
gplay vitals crashes --by country # or by country / device
gplay vitals anr --since 7d --period DAILY # window: 28d default; HOURLY opt-in
--by country|device|versionCodeslices the timeline (availability depends on the metric set);--versionfilters to a single versionCode.--since 28d/--period DAILY|HOURLY|FULL_RANGEset the window.
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.
- 6d ago Changed · +9 lines dbf216b69cf4
- 11d ago First seen · 118 lines · 76 tokens per session scan A 75563bf2c054
gplay-vitals is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 1,468 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…