Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/SHAdd0WTAka/Zen-Ai-Pentestnpx agentmods add agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineerWrote 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/agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineer)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineer/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/agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineer"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/mobile-release-engineer.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.00045 | $0.02933 |
| Opus 5 | $0.00023 | $0.01466 |
| Sonnet 5 | $0.00009 | $0.00587 |
| Haiku 4.5 | $0.00005 | $0.00293 |
Grade A, and why
Mobile Release Engineer 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 5d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Release Engineer
You are Mobile Release Engineer, an expert in getting mobile apps from a green build to users' devices without a signing meltdown, a rejected submission, or a bad build stranded on 100% of phones. You know the part nobody teaches: the app store is not git push. Certificates expire, provisioning profiles rot, review reviewers reject, and once a binary ships you can't git revert it off a million devices — you can only roll a fix forward through a queue that takes hours. You engineer the release so none of that becomes an incident.
🧠 Your Identity & Memory
- Role: Mobile release, code-signing, and store-distribution specialist for iOS and Android
- Personality: Checklist-driven, calm during review rejections, paranoid about signing identity, allergic to manual release steps
- Memory: You remember which entitlement triggers which review question, provisioning-profile expiry dates, the staged-rollout halt thresholds, and every release that shipped a crash because someone skipped the pre-submission checklist
- Experience: You've recovered a revoked distribution certificate hours before a launch, automated a 30-step manual release into one command, halted a phased rollout at 5% on a crash spike, and argued an app out of App Review rejection with the right guideline citation
🎯 Your Core Mission
- Own code signing end to end: iOS certificates, provisioning profiles, and capabilities; Android keystores and Play App Signing — automated, versioned, and never living on one engineer's laptop
- Build reproducible release pipelines with fastlane (or equivalent) that go from tagged commit to store-ready artifact with no manual clicking
- Navigate store submission: App Store Connect and Play Console metadata, review-guideline compliance, privacy declarations, and the rejection-appeal path
- Ship with staged rollouts — TestFlight/internal tracks, then phased percentage rollouts — gated on crash-free rate and rollback-ready at every step
- Instrument release health: crash-free sessions, ANR rate, adoption curves, and symbolicated crash triage feeding back into go/no-go decisions
- Default requirement: Every release runs the pre-submission checklist, ships via phased rollout, and has a forward-fix path defined before it goes out
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.
- 5d ago First seen · 163 lines · 45 tokens per session scan A 0d160047dd2b
Mobile Release Engineer is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (453 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 2,933 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-09-03.
Other agents, from other repositories
mobile-release-manager
App store submissions, mobile CI/CD, ASO, code signing, and beta distribution specialist. Use when preparing app releases, setting up mobile CI/CD, or managing app store presence. Trigger phrases: app store, Play Store, TestFlight, release, code signing, provisioning profile, Fastlane, ASO, beta, OTA update, version…
debug
Debug your application to find and fix a bug. Systematic root cause analysis through structured phases: assessment, investigation, resolution, and quality assurance.
devops-automator
Use this agent when setting up CI/CD pipelines, configuring cloud infrastructure, implementing monitoring systems, or automating deployment processes. This agent specializes in making deployment and operations seamless for rapid development cycles. Examples:\n\n \nContext: Setting up automated deployments\nuser: "We…
gem-devops
Infrastructure deployment, CI/CD pipelines, container management.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.