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 hanamizuki/solopreneur --skill gplay-submission-checksgit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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/hanamizuki/solopreneur/gplay-submission-checks)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/gplay-submission-checks"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/gplay-submission-checks/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/hanamizuki/solopreneur/gplay-submission-checks"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/gplay-submission-checks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.03680 |
| Opus 5 | $0.00023 | $0.01840 |
| Sonnet 5 | $0.00009 | $0.00736 |
| Haiku 4.5 | $0.00005 | $0.00368 |
Grade A, and why
gplay-submission-checks 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gplay-submission-checks — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 463 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google Play Submission Checks
Use this skill to validate everything before submitting a release to Google Play, reducing rejections and failed edits.
Preconditions
- Auth configured (
gplay auth loginorGPLAY_SERVICE_ACCOUNTenv var). - Package name known (
--packageorGPLAY_PACKAGE). - AAB/APK built and signed.
- Service account has at least "Release Manager" permission.
Prefer the First-Class Commands
The CLI has canonical, purpose-built commands. Reach for these before hand-scripting individual validators:
-
gplay validate --package <pkg>— the canonical release-readiness report. Combines local artifact/metadata/screenshot/release-note checks with remote track and listing state and Console-only follow-up items. Use--bundle,--listings-dir,--screenshots-dir,--track, and--strict(treat warnings as failures) to scope it.gplay validate \ --package com.example.app \ --bundle app-release.aab \ --track production \ --strict -
gplay preflight --file <app.aab>— offline AAB/APK compliance and hygiene. Fully decodesAndroidManifest.xml(binary AXML for APKs, aapt2 protobuf for App Bundles) and runs nine scanners:manifest,permissions,native_libs,metadata,secrets,billing,privacy,policy,size. No API calls and no credentials. Exit codes: 0 clean, 1 findings at/above--fail-on.gplay preflight --file app-release.aab --max-size 150M --fail-on warning # Validate the store listing in the same pass gplay preflight --file app-release.aab --listings-dir ./metadata --fail-on error # Narrow the gate gplay preflight --file app-release.aab --only manifest,permissions,native_libsSee the
gplay-preflightskill for what each scanner catches, how to read the findings, and CI gating patterns. -
gplay checks upload— Google Checks compliance analysis as a CI gate. Use--severity-threshold PRIORITYto fail the pipeline on high-priority failed checks before release.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 463 lines · 45 tokens per session scan A f49c4d852511
gplay-submission-checks is a skill published in the GitHub repository hanamizuki/solopreneur (149 stars, last pushed 27d ago), licensed MIT. It adds 45 tokens to every session and 3,680 once invoked, about $0.0002 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-30.
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.