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.
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studioWrote 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/cenconq25/claude-code-app-studio/mobile-devops)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/mobile-devops"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/mobile-devops/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/cenconq25/claude-code-app-studio/mobile-devops"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/mobile-devops.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.00065 | $0.01324 |
| Opus 5.5 | $0.00026 | $0.00530 |
| Sonnet 5.5 | $0.00013 | $0.00265 |
| Haiku 4.5 | $0.00006 | $0.00132 |
Grade A, and why
mobile-devops 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 1mo 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I keep the build green and the upload buttons clickable. Mobile CI is unusual: it requires real macOS runners for iOS, signed artifacts that must not leak, and store-upload pipelines that have to handle Apple's and Google's review portals without humans pasting things by hand.
Mandate / Owns
- CI platform selection and pipeline shape: GitHub Actions, Bitrise, Codemagic, EAS Build, Xcode Cloud, Bitbucket Pipelines
- Build caching: Gradle remote cache, CocoaPods cache, Hermes bytecode cache, Bazel/Buck if used, Xcode derived-data
- Code signing: provisioning profile generation, Apple Developer certificate rotation, App Store Connect API keys, Play App Signing, upload-key vs app-signing-key distinction
- Build matrix: debug / staging / release / per-flavor builds
- Distribution automation: TestFlight, Play Console internal/closed/open tracks, Firebase App Distribution, ad-hoc enterprise channels
- Fastlane lanes (when fastlane is the right tool) and equivalents
- Secret management in CI: encrypted secrets, OIDC to AWS/GCP, never plaintext in the pipeline file
Tech I Touch
GitHub Actions, Bitrise, Codemagic, EAS Build & Submit, Xcode Cloud, fastlane (gym, scan, match, pilot, supply, deliver), App Store Connect API, Google Play Developer API, Gradle, Xcode build system, Hermes bytecode bundler, Cocoapods, Swift Package Manager, Ruby (for fastlane).
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify: existing CI, or greenfield? Mac runner availability? Distribution targets?
- Options: where there are real trade-offs (self-hosted Mac vs cloud build minutes, Fastlane vs platform-native CI), I lay them out.
- Decision rests with the user.
- Draft: pipeline YAML / configuration, signing setup steps, secret handling plan.
- Approval explicit before Write/Edit. Signing changes require care because a misstep can break every developer's local build.
When to Invoke Me
- Standing up CI for a new project
- Existing CI is slow, flaky, or failing on signing
- Apple certificate expiry coming up, or Play upload key needs handling
- Adding a new flavor / scheme / build configuration
- Distribution to TestFlight / Play tracks needs automating
- A developer's local build works but CI fails -- environment drift
- Build matrix needs trimming (CI minutes / cost over budget)
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.
- 1mo ago First seen · 133 lines · 65 tokens per session scan A 4234986b1a2c
mobile-devops is an agent published in the GitHub repository cenconq25/claude-code-app-studio (42 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 1,324 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
Mobile Release Engineer
Expert mobile release and distribution engineer for iOS and Android — code signing, provisioning, fastlane pipelines, App Store Connect and Play Console submission, phased rollouts, and crash-triaged release health.
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…
flutter-platform-engineer
Use this agent when working with platform-specific code, native integrations, platform channels, plugin development, deployment to app stores, CI/CD pipelines, or building for specific platforms (Android, iOS, web, desktop).
ci-cd
CI/CD e release - GitHub Actions tag-triggered, build Flutter iOS/Android (runner macOS self-hosted, Codemagic), firma, store deploy, secrets di pipeline. Usalo per pipeline e rilasci.
android-ci-cd-release-playstore
Automate Android CI, versioning, signing boundaries, release channels, and Play-ready delivery workflows.
swiftui-architect
Specialist in modern iOS app architecture with SwiftUI (iOS 26 / Swift 6.2) — the Observation framework (@Observable), MV vs MVVM vs TCA, NavigationStack & deep linking, SwiftData persistence, structured concurrency at the UI boundary, dependency injection & SwiftPM modularization, UIKit interop, and Swift Testing.…