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 SteveGJones/ai-first-sdlc-practices --skill android-play-releasegit clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/android-play-release)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/android-play-release"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/android-play-release/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/stevegjones/ai-first-sdlc-practices/android-play-release"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/android-play-release.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.00059 | $0.00923 |
| Opus 5 | $0.00030 | $0.00462 |
| Sonnet 5 | $0.00012 | $0.00185 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
android-play-release 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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Play Release
Get an Android build onto Google Play without the classic policy/upload blockers, and release it with a
safety lever. Belongs to the play-store-release-specialist discipline. Run it before every Play
upload; the checks are cheap and the failures are expensive (rejection or a bad rollout).
Arguments
path-to-android-project— the project directory to check (defaults to the current directory).
Steps
1. Run the pre-flight checks
python -m android_preflight.cli <project-dir> [--play-min-target N]
Resolve every ERROR before uploading, and run ./gradlew lint (the checker doesn't reimplement
Android Lint). The checker flags:
- Sensitive permissions — background location is an ERROR (needs a Play declaration with one core feature + demo video); other restricted permissions are warnings.
- Exported components with no permission/intent-filter (any app can invoke them).
- targetSdk below the Play minimum (blocks new apps/updates; hidden on new devices — version-sensitive).
- Release config — no R8 (
minifyEnabled), debug signing config, or committed secrets. debuggable/usesCleartextTrafficin the manifest.
2. Clear the Play policy/console gates
- Data Safety form completed and matching app + third-party-SDK behaviour (mismatch = rejection).
- Account deletion (in-app + web URL) if the app has accounts; privacy policy URL live; content rating (IARC); ads/target-audience declarations.
- Sensitive-permission declarations with justification + demo video where required.
3. Build a signed app bundle
versionCodeunique & monotonic — stamp fromgit rev-list --count HEAD(or CI build number)../gradlew bundleRelease→ a signed.aab(Play requires the bundle format). Verify locally with bundletool (build-apks/install-apks) — the exact split APKs Play will serve.
4. Upload to a track and roll out deliberately
- Upload to internal testing first (available in minutes, no review) to smoke-test; then closed/ open (external needs the metadata above); then production.
- On production, use a staged (percentage) rollout starting small (e.g. 5–10%), and watch Android vitals (user-perceived crash ≥1.09% overall / ≥8% per-device, ANR ≥0.47% / ≥8% gate discoverability).
- Automate via the Play Developer API (edits flow: insert → bundles.upload → tracks.update →
commit), Gradle Play Publisher (
com.github.triplet.play), or fastlanesupply— all with service-account JSON auth.
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.
- 6d ago First seen · 75 lines · 59 tokens per session scan A f44a9db2d0b2
android-play-release is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 923 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-09-03.
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.
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"…
android-pentest
A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.