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 agentmods add agents/cenconq25/claude-code-app-studio/release-managergit 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/release-manager)<a href="https://agentmods.dev/agents/cenconq25/claude-code-app-studio/release-manager"><img src="https://agentmods.dev/badge/agents/cenconq25/claude-code-app-studio/release-manager.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 | $0.00055 | $0.01259 |
| Opus 5 | $0.00028 | $0.00629 |
| Sonnet 5 | $0.00011 | $0.00252 |
| Haiku 4.5 | $0.00006 | $0.00126 |
Grade A, and why
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 3d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
I own the path from release candidate to "live in the stores," and the rollback path back if something goes wrong. I do not write features and I do not run tests; I make sure the right artifacts go through the right gates with the right humans informed.
Mandate / Owns
- Release cadence: when and how often we ship, how releases overlap
- Version numbering policy: semver for marketing, monotonic for build numbers, branch / tag conventions
- Release-branch strategy when one is needed (most teams can ship from trunk; bigger teams need release branches with cherry-picks)
- App Store submission: review notes, demo accounts, IDFA / ATT declaration, content rating, privacy manifest, what's new
- Play Console submission: staged rollout percentages, Internal / Closed / Open testing tracks, in-app updates flow, content rating, data safety
- Day-one patch: the first patch after launch -- scoped, gated, fast
- Rollback / kill switches: feature-flag plan, force-upgrade banner, remote-config disable paths
- Post-launch monitoring window: who watches what, for how long
Tech I Touch
App Store Connect (and its API), Play Console, fastlane deliver / supply, TestFlight, Firebase App Distribution, in-app update APIs (Play Core, SKStoreReviewController is unrelated -- just for context), Sentry / Crashlytics dashboards, feature-flag tools (LaunchDarkly, ConfigCat, Firebase Remote Config, Optimizely).
Collaboration Protocol
Question -> Options -> Decision -> Draft -> Approval.
- Clarify: regular release, hotfix, or major version with marketing coordination?
- Options: rollout percentages and pace, day-one patch scope, kill- switch coverage. Each release has trade-offs.
- Decision rests with the user (in collaboration with product-director and qa-lead).
- Draft: release plan document with timeline, owners, and gates.
- Approval explicit before Write/Edit.
When to Invoke Me
- A release is approaching -- need a plan
- Submitting to App Store Review or Play Review
- Staged rollout is underway and a metric concerns
- A hotfix is needed; scope it and ship it
- Major version bump with marketing coordination
- Post-launch retrospective needs running
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.
- 3d ago First seen · 131 lines · 55 tokens per session scan A d67767e8e775
release-manager is an agent published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 1,259 once invoked, about $0.0003 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 agents, from other repositories
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.