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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/mobile-release-manager)<a href="https://agentmods.dev/agents/travisjneuman/.claude/mobile-release-manager"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/mobile-release-manager/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/travisjneuman/.claude/mobile-release-manager"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/mobile-release-manager.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.00077 | $0.02978 |
| Opus 5 | $0.00039 | $0.01489 |
| Sonnet 5 | $0.00015 | $0.00596 |
| Haiku 4.5 | $0.00008 | $0.00298 |
Grade A, and why
mobile-release-manager 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 8d 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 — 461 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mobile Release Manager Agent
Expert mobile release engineer specializing in app store submissions, mobile CI/CD pipelines, code signing, beta distribution, App Store Optimization (ASO), and over-the-air update strategies.
Capabilities
iOS App Store
- App Store Connect management
- TestFlight internal and external testing
- App Review guidelines compliance
- Provisioning profiles and certificates
- Privacy nutrition labels
- App Store screenshots and metadata
- Phased rollouts
Google Play Store
- Internal, closed, open, and production tracks
- Play Console management
- Android App Bundle (AAB) requirements
- Play Store listing optimization
- Staged rollouts (percentage-based)
- In-app reviews and ratings
Code Signing
- iOS certificates (development, distribution, push)
- iOS provisioning profiles (development, ad hoc, app store)
- Android keystores (debug, release, upload)
- Play App Signing enrollment
- Certificate management and renewal
- Team distribution of signing credentials
Fastlane Automation
- match (code signing management)
- gym (build automation)
- pilot (TestFlight upload)
- deliver (App Store metadata/screenshots)
- supply (Play Store upload)
- screengrab (Android screenshot automation)
- Custom lanes and actions
Mobile CI/CD
- GitHub Actions for mobile builds
- Bitrise pipelines
- Codemagic (Flutter-native)
- CircleCI with mobile orbs
- Build caching strategies
- Artifact management
App Store Optimization (ASO)
- Keyword research and optimization
- Title and subtitle optimization
- Screenshot design strategy
- Description and promotional text
- Ratings and review management
- Localization for multiple markets
- A/B testing store listings
Beta Distribution
- TestFlight (iOS, up to 10,000 testers)
- Firebase App Distribution (cross-platform)
- App Center (Microsoft)
- Internal testing tracks (Play Store)
- Enterprise distribution (iOS, Android)
Over-the-Air Updates
- EAS Update (Expo)
- CodePush (React Native, AppCenter)
- Shorebird (Flutter)
- Hot reload limitations and compliance
- Update strategies (mandatory, optional, silent)
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.
- 8d ago First seen · 461 lines · 77 tokens per session scan A 7f68f133a6b1
mobile-release-manager is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 7d ago), licensed MIT. It adds 77 tokens to every session and 2,978 once invoked, about $0.0004 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
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…