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 skills/frabcd/codex-ai-game-studio/team-releasenpx skills add frabcd/codex-ai-game-studio --skill team-releasegit clone --depth 1 https://github.com/frabcd/codex-ai-game-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/frabcd/codex-ai-game-studio/team-release)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/team-release"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/team-release.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.1 | $0.00034 | $0.02313 |
| Opus 5 | $0.00017 | $0.01156 |
| Sonnet 5 | $0.00007 | $0.00463 |
| Haiku 4.5 | $0.00003 | $0.00231 |
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 2d 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.
This is a copy
88% identical to team-release — 39 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Port provenance: adapted from the pinned upstream source at
984023ddac0d5e27624f2baacde6105e45de375funder MIT; see the repository parity ledger for the exact path and blob.
Argument check: If no version number is provided:
- Read
production/session-state/active.mdand the most recent file inproduction/milestones/(if they exist) to infer the target version. - If a version is found: report "No version argument provided — inferred [version] from milestone data. Proceeding." Then confirm with
the available user-input mechanism: "Releasing [version]. Is this correct?" - If no version is discoverable: use
the available user-input mechanismto ask "What version number should be released? (e.g., v1.0.0)" and wait for user input before proceeding. Do NOT default to a hardcoded version string.
When this skill is invoked, orchestrate the release team through a structured pipeline.
Decision Points: At each phase transition, use the available user-input mechanism to present
the user with the subagent's proposals as selectable options. Write the agent's
full analysis in conversation, then capture the decision with concise labels.
The user must approve before moving to the next phase.
Phase 0: Resolve Review Mode
- If
--review [mode]was passed as an argument, use that mode. - Else read
production/review-mode.txt— use whatever is written there. - Else default to
lean.
Modes:
full— spawn all director and lead gates as describedlean— skip director gates unless they are PHASE-GATE type (CD-PHASE-GATE, TD-PHASE-GATE, PR-PHASE-GATE, AD-PHASE-GATE)solo— skip all director gate spawning entirely; run the skill without any agent gates
Store the resolved mode for use in all subsequent phases.
Team Composition
- release-manager — Release branch, versioning, changelog, deployment
- qa-lead — Test sign-off, regression suite, release quality gate
- devops-engineer — Build pipeline, artifacts, deployment automation
- security-engineer — Pre-release security audit (invoke if game has online/multiplayer features or player data)
- analytics-engineer — Verify telemetry events fire correctly and dashboards are live
- community-manager — Patch notes, launch announcement, player-facing messaging
- producer — Go/no-go decision, stakeholder communication, scheduling
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 172 lines · 34 tokens per session scan A a9a11f0108d7
team-release is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 2,313 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to team-release, differing in 39 lines, and is treated as a copy.
Other skills, from other repositories
ship
Use when finished work needs to go out — the user says "ship it", "update docs commit and push", "commit and push", or asks "anything else we need to update?" before a release or at the end of a work session.
release
Project release helper for corezoid-ai-plugin. Prepares a new tagged release end-to-end. Use this skill whenever the user says "release", "релиз", "новый релиз", "сделай релиз", "выпусти версию", "bump version", "обновить версию", "tag a release", "/release", or anything that implies cutting a new version of this…
changelog
Record shipped work in the monthly changelog (append-only). Use when something ships or when asked "what changed", "add to changelog", "release notes", or "what shipped this month".
codexkit-repository-maintenance
Use when maintaining or improving the GameStudio-CodexKIT source repository, including CI, governance, catalog, generators, adapters, packaging, documentation, versioning, or release readiness.
release-candidate-preflight
Use when a release candidate or RC needs a go/no-go readiness decision across required artifacts, test summaries, known issues, approvals, compatibility, monitoring, and rollback.
release
Publish a Unica version to the public marketplace, or resume a release that stalled part-way. Use when asked to cut, ship, promote, or finish a release, or when consumers still see an older version than the latest tag.