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 skills add cenconq25/claude-code-app-studio --skill team-releasegit 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/skills/cenconq25/claude-code-app-studio/team-release)<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/team-release"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/team-release/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/skills/cenconq25/claude-code-app-studio/team-release"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/team-release.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.00039 | $0.01993 |
| Opus 5 | $0.00019 | $0.00996 |
| Sonnet 5 | $0.00008 | $0.00399 |
| Haiku 4.5 | $0.00004 | $0.00199 |
Grade A, and why
team-release 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 6d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Release
Coordinate the four roles needed to take a build from "QA approved" through to "live in users' hands". Spawns subagents in parallel where possible, sequentially where causality requires.
Team Composition
- release-manager — owns the release plan, version bumps, store submission, rollout pacing.
- qa-lead — final sign-off, post-deploy monitoring acceptance.
- mobile-devops — build pipeline, signing, certificates, store upload, infrastructure scale-up.
- producer — communications, sign-off chase, launch comms.
Spawn each via Task with subagent_type: <role>.
Phase 1: Confirm Release Type and Scope
Parse --type (major / minor / patch / hotfix) and --version. If
either is missing, ask.
Read in parallel:
- Latest release log in
production/releases/. - Latest QA sign-off.
- Latest
/release-checklistartifact for this version. - Latest
/launch-checklistartifact (if a major launch). production/stage.txt.
Render a one-line summary of the candidate release and ask the user to confirm.
Phase 2: Release Plan via release-manager
Spawn release-manager via Task. Prompt template:
Compose a release plan for version [version]. Read the release checklist at [path] and the latest QA sign-off at [path]. Produce a staged plan covering: build prep, store submission, review window expectation, staged rollout percentages, monitoring window, and rollback triggers.
Render the plan. Use AskUserQuestion:
[A] Approve plan — proceed[B] Revise rollout pacing[C] Cancel — pre-conditions not met
Phase 3: Build and Sign via mobile-devops
Spawn mobile-devops via Task. Prompt template:
Build and sign the release artifacts for version [version]. Confirm: certificates current, provisioning profiles match, Play App Signing configured, version strings and build numbers correct, source maps / dSYMs / mapping files archived. Use the project's CI release lane (
fastlane release,eas build,flutter build appbundle, native Xcode archive, etc.). Output build IDs and artifact paths.
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.
- 6d ago First seen · 289 lines · 39 tokens per session scan A dd8e88b9a745
team-release is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 1,993 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 skills, from other repositories
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
atmos-modernization
Atmos Modernization: migrate deprecated or legacy Atmos patterns to current names, Native CI, Atmos Pro drift detection, dependencies.components, nametemplate, and declared secrets.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…