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-testers-orchestrationgit 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-testers-orchestration)<a href="https://agentmods.dev/skills/tamtom/gplay-cli-skills/gplay-testers-orchestration"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-testers-orchestration/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-testers-orchestration"><img src="https://agentmods.dev/badge/skills/tamtom/gplay-cli-skills/gplay-testers-orchestration.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.00044 | $0.01265 |
| Opus 5 | $0.00022 | $0.00633 |
| Sonnet 5 | $0.00009 | $0.00253 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
gplay-testers-orchestration 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-testers-orchestration — 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testers Orchestration for Google Play
Use this skill to assign testers to a track and promote builds through the
testing funnel. All tester changes happen inside an edit session and take
effect only after gplay edits commit.
Testing tracks
| Track | Type | Max testers | Review | Access |
|---|---|---|---|---|
internal |
Internal | 100 | No | Instant |
alpha |
Closed testing | Unlimited | No | Minutes |
beta |
Open or closed testing | Unlimited | No/Yes | Minutes |
| custom track | Closed testing | Unlimited | No | Minutes |
production |
Public | Unlimited | Yes | Days |
alpha is a closed track (invite-only), not public. Testers on internal
and closed tracks are managed by email address or by Google Group.
Tester commands
gplay testers has only three subcommands. There is no testers list — to
list the testers on a track, use testers get.
gplay testers get— read the testers on a track.gplay testers update— replace the entire tester set (emails/groups not included are removed).gplay testers patch— merge with the existing set (preserves fields you omit).
List (get) testers for a track
gplay testers get \
--package com.example.app \
--edit $EDIT_ID \
--track alpha
Assign testers (replace the whole set)
gplay testers update \
--package com.example.app \
--edit $EDIT_ID \
--track alpha \
--emails "[email protected],[email protected]"
By Google Group instead of individual emails:
gplay testers update \
--package com.example.app \
--edit $EDIT_ID \
--track alpha \
--google-groups "[email protected],[email protected]"
Add testers without dropping existing ones (patch)
gplay testers patch \
--package com.example.app \
--edit $EDIT_ID \
--track alpha \
--emails "[email protected]"
Remove a tester (update = replace with the reduced set)
update replaces the resource, so re-send only the testers you want to keep:
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 · 168 lines · 44 tokens per session scan A 070c43aca2fd
gplay-testers-orchestration is a skill published in the GitHub repository tamtom/gplay-cli-skills (45 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 1,265 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-testers-orchestration, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
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.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…