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-user-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-user-management)<a href="https://agentmods.dev/skills/tamtom/gplay-cli-skills/gplay-user-management"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-user-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-user-management"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-user-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.00042 | $0.01494 |
| Opus 5 | $0.00021 | $0.00747 |
| Sonnet 5 | $0.00008 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00149 |
Grade A, and why
gplay-user-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 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.
This is a copy
100% identical to gplay-user-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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User & Grant Management
Manage team members and their permissions in Google Play Console. Two layers:
- Users (
gplay users) — account-wide members. Permissions here (*_GLOBAL,CAN_SEE_ALL_APPS) apply across the whole developer account. - Grants (
gplay grants) — per-app access for a user. Permissions here apply to a single package only.
Use users to add someone to the account (optionally with account-wide powers). Use grants to give an existing user access to specific apps without granting account-wide reach. Least privilege: prefer per-app grants over global permissions.
Preconditions
- Credentials set (
gplay auth loginorGPLAY_SERVICE_ACCOUNT). - Service account needs permission to manage users (
CAN_MANAGE_PERMISSIONS_GLOBAL). - Developer ID is required for every command. Pass it with
--developer. Find it in the Play Console URL (play.google.com/console/u/0/developers/<DEVELOPER_ID>/...).
Key concepts
- The flag is
--developer(Developer ID), not--developer-id. - There is no
--roleor--permissionsflag. Permissions are supplied as a JSON body via--json. --jsonaccepts an inline JSON string or@path/to/file.json.- Users JSON key:
developerAccountPermissions(account-wide). Grants JSON key:appLevelPermissions(per-app). deleterequires--confirm— it is a no-op safety guard, and the deletion is irreversible.
Users (account-wide)
# List users
gplay users list --developer DEVELOPER_ID
gplay users list --developer DEVELOPER_ID --paginate --page-size 50
gplay users list --developer DEVELOPER_ID --output table
# Create a user (inline JSON)
gplay users create \
--developer DEVELOPER_ID \
--email [email protected] \
--json '{"developerAccountPermissions":["CAN_SEE_ALL_APPS"]}'
# Create with an expiration and JSON from a file
gplay users create \
--developer DEVELOPER_ID \
--email [email protected] \
--json @perms.json
# Update a user's account-wide permissions
gplay users update \
--developer DEVELOPER_ID \
--email [email protected] \
--json '{"developerAccountPermissions":["CAN_SEE_ALL_APPS","CAN_VIEW_FINANCIAL_DATA_GLOBAL"]}'
# Delete a user (requires --confirm)
gplay users delete \
--developer DEVELOPER_ID \
--email [email protected] \
--confirm
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 · 173 lines · 42 tokens per session scan A 0c47a62d52ce
gplay-user-management is a skill published in the GitHub repository tamtom/gplay-cli-skills (45 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 1,494 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gplay-user-management, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
orca-emulator-android
Android device and emulator control from inside Orca over adb, with the live device view in Orca's emulator pane. Use when driving an adb-connected emulator or phone on Windows, Linux, or macOS: booting AVDs, taps, swipes, typing, hardware buttons, rotation, app install and launch, runtime permissions, the…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
react-native-ease-refactor
Scan for Animated/Reanimated code and migrate to EaseView.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…