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-metadata-syncgit 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-metadata-sync)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-metadata-sync"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-metadata-sync/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-metadata-sync"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-metadata-sync.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.00066 | $0.01495 |
| Opus 5 | $0.00033 | $0.00747 |
| Sonnet 5 | $0.00013 | $0.00299 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
gplay-metadata-sync 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 4d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay metadata sync (listings + images)
Manage the store front: per-locale listing text and images, kept as an
on-disk tree and reconciled with Play. Shared conventions (auth, --package,
output, exit codes) are in gplay-cli-usage.
The sync model
gplay treats a local ./metadata tree (<locale>/<field>.txt, plus image
files) as the desired state and reconciles it with Play (ADR-0011). The loop:
pull → edit on disk → validate (offline) → apply --dry-run → apply --confirm
metadata pullrapatriates the live Listings into the tree (<locale>/title.txt,short_description,full_description,video). It reads inside a read-only Edit (nothing committed) and is additive, a field empty online writes no file, a local locale absent online is left intact. Ametadata applyimmediately after apullis a guaranteed no-op.metadata validatelints the tree offline (no auth, no network): character limits (title 30, short 80, full 4000), required non-empty fields (title + full description), and known Play locale codes. Any violation exits20. Safe in a pre-commit hook or CI gate. (--allow-locale xx-YYwhitelists a locale Google added after this gplay release.)metadata applyreconciles disk → Play. Additive by default: it upserts the locales/fields on disk and leaves online-only locales intact (reported).--prunealso deletes online-only locales (it refuses to remove the app'sdefaultLanguage). Note a locale counts as "present on disk" only if its directory holds at least one recognized field file, a folder with only a README is not managed, and under--prunewould be deleted online.metadata listsummarizes what is live on Play, per locale.
Apply safely
gplay metadata pull --dir ./metadata
# …edit the .txt files…
gplay metadata validate --dir ./metadata # offline lint, exit 20 on error
gplay metadata apply --dir ./metadata --dry-run # ONLINE diff, prints per-locale delta
gplay metadata apply --dir ./metadata --confirm # publishes, live immediately
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.
- 4d ago Changed · +13 lines 45b040bcc956
- 9d ago First seen · 95 lines · 66 tokens per session scan A 206b62169a9a
gplay-metadata-sync is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 1,495 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
flutter-setup-localization
Add flutterlocalizations and intl dependencies, enable "generate true" in pubspec.yaml, and create an l10n.yaml configuration file. Use when initializing localization support for a new Flutter project.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
ios-marketing-capture
Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…
localization-l10n
Implement localization (l10n) best practices to adapt applications for specific regions, languages, and cultural preferences.
maui-localization-theming
Implement MAUI localization and theming. USE FOR: RESX/AppResources, runtime culture switching, RTL/FlowDirection, platform language metadata, AppThemeBinding, DynamicResource, light/dark/system themes, UserAppTheme. DO NOT USE FOR: general layout, accessibility audits, icon/splash assets.