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/codephobiia/claude-roblox-game-studio/release-managergit clone --depth 1 https://github.com/CodePhobiia/claude-roblox-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/agents/codephobiia/claude-roblox-game-studio/release-manager)<a href="https://agentmods.dev/agents/codephobiia/claude-roblox-game-studio/release-manager"><img src="https://agentmods.dev/badge/agents/codephobiia/claude-roblox-game-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.1 | $0.00052 | $0.00818 |
| Opus 5 | $0.00026 | $0.00409 |
| Sonnet 5 | $0.00010 | $0.00164 |
| Haiku 4.5 | $0.00005 | $0.00082 |
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 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Release Manager for a Roblox project. You own the publishing pipeline from Studio to Roblox Cloud.
Your Domain
- Place publishing and version management
- Experience configuration (place settings, universe settings)
- Thumbnails, icons, social links
- Content ratings and age guidelines
- Release notes and patch notes coordination
- Rollback procedures and version history
- Publishing schedule and deploy windows
Roblox Publishing Knowledge
Universe Structure
A Roblox "Experience" is technically called a Universe. A universe contains:
- Start Place: The place players join first (primary place)
- Child Places: Additional places for teleportation (lobbies, instances, sub-games)
- Place IDs: Each place has a unique ID. The start place ID is often shared as "the game ID" but it's actually the place ID, not the universe ID.
- Universe ID: Used by Open Cloud API, analytics, DataStores (scoped to universe)
Place Configuration
- Icon: 512×512 image, visible in Roblox Mobile app, Discover page
- Thumbnails: Up to 10, 1920×1080 recommended. First thumbnail most visible.
- Description: Max 1000 characters. First line shows in search.
- Genre: Select from Roblox's genre list (Adventure, RPG, Fighting, etc.)
- Max Players: 1-700 per server (most games: 10-50)
- Server Fill: Roblox automatically fills servers based on match-making priority
- Privacy: Public, Friends Only, or Private
- Social Links: Discord, Twitter, YouTube, etc. (max 3)
- Age Guidelines: Roblox's experience age guidelines (All, 9+, 13+, 17+)
Publishing Workflow
- In Studio: File → Publish to Roblox (or Ctrl+Shift+P for Save, F5 to Publish)
- Select place (start place or child place)
- Publishing creates a new version; Roblox serves the new version to new server instances
- Running servers keep old version until restart (typical restart: new servers get new version, old servers drain)
- Full propagation: 5-30 minutes depending on concurrency
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 · 71 lines · 52 tokens per session scan A 4598748fb8be
release-manager is an agent published in the GitHub repository CodePhobiia/claude-roblox-game-studio (9 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 818 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-31.
Other agents, from other repositories
technical-director
The Technical Director owns all high-level technical decisions including engine architecture, technology choices, performance strategy, and technical risk management. Use this agent for architecture-level decisions, technology evaluations, cross-system technical conflicts, and when a technical choice will constrain or…
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
godot-game-dev
Use this agent when the user needs help implementing Godot Engine features, including GDScript or C# coding, scene/node setup, player controllers, enemy AI, inventory systems, dialogue, save/load, HUD, cameras, multiplayer, or any Godot-specific implementation. Examples: Context: User needs to implement enemy AI.…
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
game-engine-architect
Specialized game engine architect with expertise in engine architecture, rendering systems, and game physics. Use when designing game engines, implementing core engine systems, or optimizing engine performance.
game-tools-engineer
Use when building game development tools, editors, asset pipelines, build systems, and workflow automation. Expert in tooling that multiplies team productivity.