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 zurche/agent-skills --skill android-release-bumpgit clone --depth 1 https://github.com/zurche/agent-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/zurche/agent-skills/android-release-bump)<a href="https://agentmods.dev/skills/zurche/agent-skills/android-release-bump"><img src="https://agentmods.dev/badge/skills/zurche/agent-skills/android-release-bump.svg" alt="Measured on agentmods" 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.00091 | $0.00789 |
| Opus 5 | $0.00046 | $0.00394 |
| Sonnet 5 | $0.00018 | $0.00158 |
| Haiku 4.5 | $0.00009 | $0.00079 |
Grade A, and why
android-release-bump 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 7d 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Android Release Bump
Workflow
- Validate preconditions: run on
main, require clean working tree, requirekeystore.properties, and requireplay-api-key.jsononly when upload is requested. - Resolve app name in this order: existing tag prefix,
settings.gradle.ktsrootProject.name,app/build.gradle.ktsnamespaceorapplicationId, then ask the user. - Read current
versionNameandversionCodefromapp/build.gradle.kts. - Discover the latest release tag and commits since that tag.
- Recommend
major,minor, orpatchusing references/versioning.md, then wait for explicit confirmation. - Update
versionNameand incrementversionCodeby+1from its current configured value. - Detect locales, generate
app/src/main/play/release-notes/<locale>/default.txt, and enforce limits from references/locales.md. - Show release notes for review, then wait for explicit confirmation before committing.
- Run verification:
./gradlew assembleDebug && ./gradlew detekt && ./gradlew test. - If device or emulator QA is requested, load references/emulator-validation.md. Prefer a headless AVD with
-no-windowfor scripted smoke checks, keep it running while you iterate withadb, and only shut it down when validation is complete or the user asks. - Commit release notes and version bump as separate commits, then create annotated tag
v<app-name>-X.Y.Z. - Show pre-push summary and wait for explicit confirmation before pushing
mainand the tag. - Build signed bundle with
./gradlew :app:copyReleaseBundle. - Create a GitHub release with
gh release create <tag> --title "<tag>" --notes "<en-US release notes>" --target main. - If upload is requested, show upload plan and wait for explicit confirmation before
./gradlew publishReleaseBundle. - Print completion summary format from references/recovery.md.
Mandatory Confirmations
What ships with it
5 files 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.
- 7d ago First seen · 50 lines · 91 tokens per session scan A fcb3d9c6495f
android-release-bump is a skill published in the GitHub repository zurche/agent-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 789 once invoked, about $0.0005 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
release-new-version
Use when the user wants to release a new Zafiro version — drafting bilingual release notes, deciding the next version number, bumping app/build.gradle.kts, tagging, and publishing to GitHub (main repo, optionally the Xposed repo).
managing-app-versions
Manages semantic versioning for mobile apps across iOS and Android platforms. Use when the user says "bump version", "increment build number", "set version to", "release patch/minor/major", or "sync build numbers". Single source of truth is .msd/versions/{app-id}/version.json. Syncs to app.json (Expo), Info.plist…
submitting-app-release
Runs pre-flight validation gates and submits the app to App Store Connect and Google Play Console via EAS CLI. Use when the user says "release", "submit to store", "publish", "deploy app", or "submit for review". Always runs release-checklist.js first — never submits past a failing gate without explicit user…
kappmaker-publish
Build, sign and ship a KAppMaker app — Fastlane setup, signed Android AAB, keystore generation, and uploading to Google Play and the App Store. Use when the user asks to build a release, create a keystore, configure fastlane, ship, upload or publish the app. Building iOS without a Mac is kappmaker-ios-ci.
asc-ad-hoc-distribution
Prepare, publish, resume, and verify private iOS release-testing installs with asc distribute. Use when distributing an IPA to registered devices outside TestFlight, reconciling ad hoc profiles, publishing through caller-owned S3-compatible storage, or diagnosing a resumable private distribution run.
flame-harness-submit
Phase 10 — upload store text metadata + categories via fastlane, then pause with exact manual steps for the final iOS review submission and Android production promotion.