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-teamgit 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-team)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-team"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-team/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-team"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-team.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.00065 | $0.00895 |
| Opus 5 | $0.00032 | $0.00447 |
| Sonnet 5 | $0.00013 | $0.00179 |
| Haiku 4.5 | $0.00006 | $0.00089 |
Grade A, and why
gplay-team 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay team (users + grants + permissions)
Two write surfaces and one offline reference: account-wide membership
(team users), per-app access (team grants), and the permission
vocabulary (team permissions). Shared conventions (auth, output, exit
codes) are in gplay-cli-usage.
Permission vocabulary (start here)
gplay team permissions # account-scope aliases + role bundles
gplay team permissions --scope app # the per-app enum family
gplay team permissions --output json # marks the admin-conferring alias/bundle
team permissions is offline (no API call, no credential) and is the
single source of truth the write commands resolve --role / --permissions
through (ADR-0016). It lists the curated aliases and the frozen role
bundles: viewer, reviewer, tester-manager, release-manager, admin.
Writes express permissions in friendly form, --role <bundle> XOR
--permissions <alias,…>, and any raw CAN_* enum is also accepted.
--scope account resolves the account-wide _GLOBAL family (for team users); --scope app resolves the bare per-app family (for team grants).
Account-wide members
gplay team users list
gplay team users view [email protected] # one member: permissions + per-app grants
gplay team users add [email protected] --role release-manager
gplay team users set [email protected] --permissions CAN_REPLY_TO_REVIEWS_GLOBAL
gplay team users remove [email protected]
add invites a member (users.create); set declaratively replaces a
member's account-wide permissions; remove off-boards them. These are the
routine tier (CI-scriptable, no confirmation gate), except conferring
admin: --role admin (or a permission set including the all-permissions enum)
requires the named --grant-admin flag. Handing out full control is never
silent (ADR-0017).
users view <email> answers "what can this person do?" in one call: their
accessState, their account-wide permissions (admins flagged in the ADMIN
field), and one row per app grant. The Play API has no users.get, so gplay
lists the account and filters client-side, the same cost as
team grants list --user. A member who is not on the account exits 30, so
team users list is the way to see who is.
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 · 79 lines · 65 tokens per session scan A 731e884498b4
gplay-team is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 895 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
field-service
Build ServiceNow Field Service Management — wmorder work orders, wmtask tasks, wmresource technicians with skills/territories, dispatch/auto-assignment, mobile status updates, and time entries.
expo-eas-submit
App Store Connect and Google Play Console upload flow with EAS Submit, metadata, build-artifact selection, review notes, and phased release. Triggers on eas submit, app store connect, google play, asc api key, service account, metadata, screenshot, phased release, review notes, testflight, internal testing, production…
asc-submission
Prepare an app for App Store submission or TestFlight distribution using the App Store Connect MCP server. Use when user says "prepare submission", "submit to app store", "prepare for review", "update metadata", "set what's new", "check submission readiness", "distribute to testflight", or wants to manage App Store…
app-store-prep
When preparing a release build or responding to rejection reasons.
app-store-launch-orchestrator
Coordinate an Apple app from idea research through specification, design, development, testing, App Store Connect, compliance, review recovery, release, and post-launch measurement. Use when the user asks to create, finish, ship, publish, launch, or assess an iPhone, iPad, macOS, watchOS, tvOS, or visionOS app; when…
dev-story
Read a story file and implement it end-to-end. Loads PRD requirement, governing ADR, control manifest, and routes to the right framework specialist (RN/Flutter/iOS/Android). Use when a story has passed /story-readiness and is ready to be built.