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 frabcd/codex-ai-game-studio --skill team-live-opsgit 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-live-ops)<a href="https://agentmods.dev/skills/frabcd/codex-ai-game-studio/team-live-ops"><img src="https://agentmods.dev/badge/skills/frabcd/codex-ai-game-studio/team-live-ops.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.00057 | $0.02259 |
| Opus 5 | $0.00028 | $0.01130 |
| Sonnet 5 | $0.00011 | $0.00452 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
team-live-ops 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 4d 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
91% identical to team-live-ops — 31 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 — 163 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 season name or event description is provided, output:
"Usage:
$ai-game-studio:team-live-ops [season name or event description]— Provide the name or description of the season or live event to plan." Then stop immediately without spawning any subagents or reading any files.
When this skill is invoked with a valid argument, orchestrate the live-ops team through a structured planning 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
- live-ops-designer — Season structure, event cadence, retention mechanics, battle pass
- economy-designer — Live economy balance, store rotation, currency pricing, pity timers
- analytics-engineer — Success metrics, A/B test design, event tracking, dashboard specs
- community-manager — Player-facing announcements, event descriptions, seasonal messaging
- narrative-director — Seasonal narrative theme, story arc, world event framing
- writer — Event descriptions, reward item names, seasonal flavor text, announcement copy
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.
- 4d ago First seen · 163 lines · 57 tokens per session scan A 6faae3416fe7
team-live-ops is a skill published in the GitHub repository frabcd/codex-ai-game-studio (9 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 2,259 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to team-live-ops, differing in 31 lines, and is treated as a copy.
Other skills, from other repositories
release-checklist
Generates a comprehensive pre-release validation checklist covering build verification, certification requirements, store metadata, and launch readiness.
3d_object
Judge whether a generated mesh is fit to ship in a browser game, from the same rendered sheet the orientation review uses.
audio
Use this Skill when a game plan requires dialogue, voice lines, sound effects, foley, ambience, or other offline WAV assets. This is asset generation, not a runtime audio-playback contract; use the selected engine context after an asset has passed review.
game-build
Build a risk-matched whitebox or the approved production game for its target runtime. Turn GAMEDESIGN, and ARTDIRECTION when production begins, into a minimal BUILDBRIEF and a runnable candidate that can be iterated with replayable evidence. Use for prototype the riskiest design question, implement the approved game…
novel-to-game
Turn a novel into a fully playable game on the selected target platform. Orchestrates the whole adaptation pipeline — requirements intake, gameable deconstruction, concept selection, world and visual design, target-runtime build, and evidence-based QA — for a novel in any language. Use for novel to game, story to…
team-combat
Orchestrate the combat team: coordinates game-designer, gameplay-programmer, ai-programmer, technical-artist, sound-designer, and qa-tester to design, implement, and validate a combat feature end-to-end.