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 tamtom/gplay-cli-skills --skill gplay-rollout-managementgit clone --depth 1 https://github.com/tamtom/gplay-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/tamtom/gplay-cli-skills/gplay-rollout-management)<a href="https://agentmods.dev/skills/tamtom/gplay-cli-skills/gplay-rollout-management"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-rollout-management/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/tamtom/gplay-cli-skills/gplay-rollout-management"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-rollout-management.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.00025 | $0.01664 |
| Opus 5 | $0.00013 | $0.00832 |
| Sonnet 5 | $0.00005 | $0.00333 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
gplay-rollout-management 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 11d 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.
This is a copy
100% identical to gplay-rollout-management — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Staged Rollout Management
Use this skill when you need to manage gradual releases on Google Play.
What is Staged Rollout?
Staged rollout releases your app to a percentage of users, allowing you to:
- Monitor crash rates and reviews before full release
- Catch critical bugs with limited user impact
- Gradually increase distribution as confidence grows
Start a Staged Rollout
During initial release
gplay release \
--package com.example.app \
--track production \
--bundle app-release.aab \
--rollout 0.1
This releases to 10% of users.
Promote with rollout
gplay promote \
--package com.example.app \
--from beta \
--to production \
--rollout 0.25
Increase Rollout Percentage
# Increase to 25%
gplay rollout update \
--package com.example.app \
--track production \
--rollout 0.25
# Increase to 50%
gplay rollout update \
--package com.example.app \
--track production \
--rollout 0.5
# Increase to 100% (or use complete)
gplay rollout update \
--package com.example.app \
--track production \
--rollout 1.0
Halt Rollout
Pause distribution if issues are detected:
gplay rollout halt \
--package com.example.app \
--track production
Effect:
- Stops further distribution
- Existing users keep the update
- New users don't receive the update
Resume Rollout
Resume after fixing issues:
gplay rollout resume \
--package com.example.app \
--track production
Complete Rollout
Release to 100% of users:
gplay rollout complete \
--package com.example.app \
--track production
Check Rollout Status
gplay tracks get \
--package com.example.app \
--track production \
| jq '.releases[0].userFraction'
Recommended Rollout Strategy
Conservative (7-day rollout)
# Day 1: 10%
gplay release --package com.example.app --track production --bundle app.aab --rollout 0.1
# Day 2: 25% (monitor crash rate)
gplay rollout update --package com.example.app --track production --rollout 0.25
# Day 3: 50%
gplay rollout update --package com.example.app --track production --rollout 0.5
# Day 5: 75%
gplay rollout update --package com.example.app --track production --rollout 0.75
# Day 7: 100%
gplay rollout complete --package com.example.app --track production
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.
- 11d ago First seen · 271 lines · 25 tokens per session scan A 325cb200705e
gplay-rollout-management is a skill published in the GitHub repository tamtom/gplay-cli-skills (45 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,664 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gplay-rollout-management, differing in 0 lines, and is treated as a copy.
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…