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-compliancegit 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-compliance)<a href="https://agentmods.dev/skills/pollyglot/google-play-cli-skills/gplay-compliance"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-compliance/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-compliance"><img src="https://agentmods.dev/badge/skills/pollyglot/google-play-cli-skills/gplay-compliance.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.00055 | $0.00619 |
| Opus 5 | $0.00028 | $0.00309 |
| Sonnet 5 | $0.00011 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
gplay-compliance 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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
gplay compliance (Data Safety)
Manage the app's Data Safety declaration from a canonical CSV. Shared
conventions (auth, --package, output, exit codes) are in gplay-cli-usage.
What is and isn't automatable (the hard wall)
Data Safety is the only Play compliance surface with a Developer API endpoint. These neighbouring declarations have no API and cannot be driven by gplay; they remain manual in the Play Console:
- Content rating (IARC questionnaire)
- Target audience & content / Families
- Ads declaration, News-app declaration, Government-app status, COVID-19, etc.
Treat those as a documented manual step in your release runbook; gplay does not and will not automate them. This skill is strictly about Data Safety.
Data Safety is write-only
The declaration is write-only (ADR-0014): a direct POST outside the
Edits model that replaces the whole document. gplay cannot read it back;
there is no get, only set and an offline validate. The live POST is the
only thing that validates the contents against Google's schema.
gplay compliance datasafety validate # offline structural check
gplay compliance datasafety set --dry-run # rehearse: validate + resolve target + size
gplay compliance datasafety set --confirm # the real write, replaces the live declaration
validatestructurally checks the CSV offline (no network, no auth).setpushes the canonical CSV (--file, default./compliance/data-safety.csv). It runsvalidateimplicitly first, so a structurally invalid CSV never reaches the network.--dry-runrehearses, validates, resolves the target package/Account, and reports "would POST N bytes / N rows" with no HTTP call (and no--confirmneeded).- The real write requires
--confirm(a stale or wrong declaration can block releases or misstate your data practices); without itsetrefuses with exit3, and the--output jsonerror envelope names the flag inrequires: ["confirm"], add it and re-run.CI=truedoes not auto-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.
- 11d ago First seen · 57 lines · 55 tokens per session scan A c6e85a36b2e9
gplay-compliance is a skill published in the GitHub repository PollyGlot/google-play-cli-skills (5 stars, last pushed 7d ago), licensed MIT. It adds 55 tokens to every session and 619 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
play-policy-insights
Automated auditor designed to verify Android applications against Google Play Policy domains. It cross-references static code analysis with Play Store declarations to generate deterministic compliance reports, identifying undeclared data collection, architectural risks, and missing disclosures across Permissions and…
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
app-store-review
Evaluates code against Apple's App Store Review Guidelines. Use this skill when reviewing iOS, macOS, tvOS, watchOS, or visionOS app code (Swift, Objective-C, React Native, or Expo) to identify potential App Store rejection issues before submission. Triggers on tasks involving app review preparation, compliance…
account-deletion
Generates an Apple-compliant account deletion flow with multi-step confirmation UI, optional data export, configurable grace period, Keychain cleanup, and server-side deletion request. Use when user needs account deletion, right-to-delete, or Apple App Review compliance for account removal.
consent-flow
Generates GDPR/CCPA/DPDP privacy consent flows with granular category preferences, consent state persistence, audit logging, and ATT (App Tracking Transparency) integration. Use when user needs privacy consent UI, cookie/tracking consent, or compliance management.
appstore-review-checker
Audit iOS/macOS apps against App Store Review Guidelines before submission, with evidence-backed verdicts and fixes. Don't use for Google Play, general code review, or rejection appeals.