What is team-release?

A coordinated workflow for publishing a Roblox game release. It brings together checks, documentation, configuration, publishing, announcements, and post-release monitoring.

Use it to verify a release, prepare changelogs and patch notes, check publishing setup, announce the update, and watch for problems after launch.

It reduces the risk of releasing with unfinished tests, security problems, broken deployment settings, or missing player communication.

team-release — Skill for Claude Code by CodePhobiia

Install

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.

Any agent

npx skills add CodePhobiia/claude-roblox-game-studio --skill team-release

Clone the repo

git clone --depth 1 https://github.com/CodePhobiia/claude-roblox-game-studio

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/team-release/github.svg)](https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-release)

Your own site

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-release"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codephobiia/claude-roblox-game-studio/team-release"><img src="https://agentmods.dev/badge/skills/codephobiia/claude-roblox-game-studio/team-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 668 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00036	$0.00668
Opus 5	$0.00018	$0.00334
Sonnet 5	$0.00007	$0.00134
Haiku 4.5	$0.00004	$0.00067

Measured 8d ago against content hash fba150858351, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 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.

.claude/skills/team-release/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/team-release — Release Publishing Team

Orchestration Flow

Releases involve many disciplines. This orchestrates them into a publish.

Phase 1: Verification

qa-lead: Verify test plan completion
exploit-security-specialist: Final security pass
performance-analyst: Final perf benchmarks
release-manager: Runs /publish-review checklist

Phase 2: Documentation

release-manager: Generate /changelog
writer: Polish technical changelog into player-facing /patch-notes
community-manager: Prep Discord / social announcements

Phase 3: Configuration

release-manager: Verify experience configuration (icon, thumbnails, description, social links)
devops-engineer: Verify CI/CD and deployment pipeline ready

Phase 4: Publish

release-manager: Execute publish
release-manager: Verify new version is live
community-manager: Publish community announcements

Phase 5: Monitor

analytics-retention-specialist: Watch metrics dashboards
qa-lead: Watch bug reports
incident-responder-style workflow: Ready for hotfix if needed

Steps

1. Gather Context

"What version?" (X.Y.Z)
"What's the theme?"
"What's the rollout strategy?" (immediate / gradual / canary)

2. Verification Phase

Run /publish-review (comprehensive checklist)
Any critical blockers → halt release until resolved
Verify all metrics targets met

3. Documentation Phase

Generate changelog
Polish into patch notes
Draft community announcements

4. Configuration Phase

Verify all Roblox experience settings
Ensure CI/CD is ready
Verify rollback plan is documented

5. Go/No-Go Decision

Present the full situation to the user:

Verification status
Documentation ready
Configuration ready
Monitoring set up
Rollback plan

User makes the final go/no-go call.

6. Publish Phase

Execute publish (via Studio or Open Cloud)
Verify new version running
Send announcements
Start monitoring

Read the full file on GitHub · 97 lines

Changes

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 · 97 lines · 36 tokens per session scan A fba150858351

Subscribe to this mod's changes

team-release is a skill published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 668 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.

Game development Git and workflow Releases

build-game-changelog

Design, implement, backfill, audit, and release in-game changelogs with contiguous versioning, deployment provenance, menu-state navigation, accessible toggle, close, and Escape behavior, and responsive release-ledger UI. Use when Codex needs to add or revise a changelog or version screen in a game, reconstruct…

MengTo/Skills · 100 tokens

team-release