Borrowing it
Nothing to install: this file belongs to ahmed3elshaer/everything-claude-code-mobile. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ahmed3elshaer/everything-claude-code-mobile/main/.opencode/commands/release-build.mdgit clone --depth 1 https://github.com/ahmed3elshaer/everything-claude-code-mobileWrote 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/commands/ahmed3elshaer/everything-claude-code-mobile/release-build)<a href="https://agentmods.dev/commands/ahmed3elshaer/everything-claude-code-mobile/release-build"><img src="https://agentmods.dev/badge/commands/ahmed3elshaer/everything-claude-code-mobile/release-build.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.00017 | $0.00334 |
| Opus 5 | $0.00009 | $0.00167 |
| Sonnet 5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
release-build 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.
What it actually says
Release Build Command
Build production-ready Android artifacts.
Usage
/release-build
/release-build apk
/release-build bundle
What It Does
- Runs lint checks
- Executes all tests
- Builds signed release
- Verifies R8 optimization
- Reports APK/AAB size
Commands
# Release APK
./gradlew assembleRelease
# App Bundle (Play Store)
./gradlew bundleRelease
# With mapping upload
./gradlew assembleRelease -PuploadMapping=true
Signing Configuration
// build.gradle.kts
android {
signingConfigs {
create("release") {
storeFile = file(keystoreProperties["storeFile"]!!)
storePassword = keystoreProperties["storePassword"]!!
keyAlias = keystoreProperties["keyAlias"]!!
keyPassword = keystoreProperties["keyPassword"]!!
}
}
buildTypes {
release {
isMinifyEnabled = true
isShrinkResources = true
proguardFiles(
getDefaultProguardFile("proguard-android-optimize.txt"),
"proguard-rules.pro"
)
signingConfig = signingConfigs.getByName("release")
}
}
}
Pre-release Checklist
- Version code/name updated
- All tests passing
- ProGuard rules verified
- Signing configured
- Analytics/crash reporting enabled
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 · 73 lines · 17 tokens per session scan A dc64d20d3c97
release-build is a command published in the GitHub repository ahmed3elshaer/everything-claude-code-mobile (65 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 334 once invoked, about $0.0001 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 commands, from other repositories
instrument
Generate a comprehensive instrumentation plan for a mobile codebase.
feat
Kick off tasks creation for a new feature (4-item interview before invoking pm-agent; an epic-sized requirement routes to phased decomposition, a feature already built on one platform routes to cross-platform parity, a change that touches no endpoint routes to client-only).
status
Project health dashboard - shows environment status and suggests improvements.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.