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-release-flowgit 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-release-flow)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-release-flow"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-release-flow/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-release-flow"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-release-flow.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.00091 | $0.03215 |
| Opus 5 | $0.00046 | $0.01607 |
| Sonnet 5 | $0.00018 | $0.00643 |
| Haiku 4.5 | $0.00009 | $0.00321 |
Grade A, and why
gplay-release-flow 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 5d 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay release flow
Drive the Google Play release lifecycle from the command line with gplay:
upload a build to a track, promote it up the ladder, run a staged
rollout on production (and halt / resume / complete it), and list
what is currently on a track. gplay hides Google's three-step Edit transaction
(edits.insert → change → edits.commit) behind a single call per command.
Shared conventions (auth setup with gplay auth doctor, --package pinning
via gplay init, --output json for machines, and the semantic exit-code
table) are in gplay-cli-usage; onboarding auth is gplay-setup. The codes
that matter most here: 3 a required --confirm is missing (re-run with it),
30 an API 4xx such as a missing track, 60 an ambiguous target (two releases
coexist), 40/50 retry-safe (5xx / network).
Mental model: the track ladder + the rollout state machine
A build is uploaded to one track (internal, alpha, beta,
production, or any custom closed-track name) and then promoted up the
ladder: the same versionCode, no AAB re-upload. On a track, the latest
release moves through a small state machine:
draft ──► inProgress (userFraction f) ──► completed (f = 1.0)
│ ▲
halt│ │resume
▼ │
halted (fraction preserved)
rollout sets the fraction, halt freezes it, resume un-freezes it, and
complete ramps to 100%.
Upload a build to a track
gplay releases upload ./app.aab --track internal
gplay releases upload ./app.aab --track production --staged 0.1 --confirm
gplay releases upload ./app.aab --track production --complete --confirm
One call runs the full Edit lifecycle (edits.insert → bundles.upload → tracks.update → edits.commit). Any string is a valid --track, so custom
closed tracks "just work", as long as the track already exists (see
Track must exist first below). Attach notes with --release-notes or a
--release-notes-dir of <locale>.txt files, and a ProGuard/R8
--mapping mapping.txt so vitals can symbolicate this build's crash stacks
(see Deobfuscation mappings below). Run gplay releases upload --help for
the full set.
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.
- 5d ago Changed · +24 lines 1be188ae95cd
- 10d ago First seen · 230 lines · 91 tokens per session scan A d8dabba91da8
gplay-release-flow is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 91 tokens to every session and 3,215 once invoked, about $0.0005 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
axiom-shipping
Use when preparing ANY app for submission, handling App Store rejections, writing appeals, or managing App Store Connect. Covers submission checklists, rejection troubleshooting, metadata requirements, privacy manifests, age ratings, export compliance.
asc-ad-hoc-distribution
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
suede-play-release
Suede Labs Google Play delivery skill: ship an Android release end to end from the agent interface, without opening the Play Console. Set up credentials, upload an AAB, promote between tracks, stage or complete a rollout, push per-locale release notes, and prove against the Play Developer API what is actually live.…
testflight-release
Ship a new TestFlight build of the iOS companion (TermioMobile) — resolve the next build number against App Store Connect, archive, sign, export, upload, write the What to Test notes, and distribute. Invoke when the user says 'ship a testflight build', 'update testflight', 'upload to testflight', 'new beta build'…
app-release
End-to-end pipeline for releasing an iOS / watchOS app to TestFlight and the App Store. Use when the user wants to publish, ship, or release an iOS/watchOS app, get a build onto TestFlight, archive and upload via xcodebuild, deploy a CloudKit schema to Production, set App Privacy or export compliance, mint a…