awesome-gamedev-agent-skills is a collection of 73 instruction files that give AI coding agents specialized guidance for game development with engines and frameworks such as Godot, Unity, Unreal, and Phaser. It helps agents choose relevant engine and task guidance while building games. The catalogue entries are the collection's skills and plugins for agents including Claude Code, Cursor, Codex, and Gemini CLI.
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 gamedev-skills/awesome-gamedev-agent-skills --skill roblox-studio-workflowgit clone --depth 1 https://github.com/gamedev-skills/awesome-gamedev-agent-skillsWrote 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/gamedev-skills/awesome-gamedev-agent-skills/roblox-studio-workflow)<a href="https://agentmods.dev/skills/gamedev-skills/awesome-gamedev-agent-skills/roblox-studio-workflow"><img src="https://agentmods.dev/badge/skills/gamedev-skills/awesome-gamedev-agent-skills/roblox-studio-workflow/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/gamedev-skills/awesome-gamedev-agent-skills/roblox-studio-workflow"><img src="https://agentmods.dev/badge/skills/gamedev-skills/awesome-gamedev-agent-skills/roblox-studio-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00096 | $0.02379 |
| Opus 5.5 | $0.00038 | $0.00952 |
| Sonnet 5.5 | $0.00019 | $0.00476 |
| Haiku 4.5 | $0.00010 | $0.00238 |
Grade A, and why
roblox-studio-workflow 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Roblox Studio workflow
Work as a collaborator inside an existing place, not as if it were a blank text repository. Targets current Roblox Studio and rolling platform APIs.
When to use
- Use before invasive edits to a Roblox place, Studio DataModel, or Rojo-backed project.
- Use to plan execution location, find/reuse systems, create editable Instances, and gather honest Studio verification evidence.
When not to use: this skill owns project operation, not the domain implementation. Compose it
with roblox-ui, roblox-networking, roblox-characters, roblox-physics, roblox-luau, or
roblox-datastores as appropriate.
Workflow
- Establish source of truth. Determine whether Studio, Rojo files, a package manager, or a generated build owns each subtree. Do not hand-edit generated output or create Studio-only changes that the next sync overwrites.
- Inventory before proposing structure. Inspect Explorer, search scripts/modules/remotes/tags, read project mapping and naming conventions, and run once to observe existing warnings. Locate the feature's current owner and dependencies.
- Plan the smallest compatible edit. Name the Instances and execution locations you will change. Reuse existing remotes, component modules, cleanup utilities, tags, Attributes, folders, and configuration patterns. State any unresolved ownership boundary.
- Create real, meaningful objects. Normal authored UI, folders, attachments, constraints, remotes, and configuration remain inspectable in Explorer. Use scripts for behavior and truly dynamic repetition—not to hide the entire feature in runtime construction.
- Respect execution and replication. Put authoritative logic in server containers, persistent
client logic in
StarterPlayerScripts, per-character client logic inStarterCharacterScripts, UI templates inStarterGui, shared assets/modules/remotes inReplicatedStorage, and secrets/server assets in server-only containers. - Test the actual risk. Choose Test, Test Here, Run, Server & Clients, Device Simulator, Controller Emulator, Network Simulator, or scripted Studio testing based on the behavior. Inspect server and client Output, not only the viewport.
- Clean the experiment. Remove temporary parts, test remotes, command-bar scripts, debug UI, prints, disabled duplicate scripts, placeholder assets, and tags/Attributes created only for diagnosis. Stop the session and confirm edit-mode hierarchy is clean.
- Report evidence precisely. List changed Instances/files, modes and client counts, cases executed, observed Output, failures and fixes, and anything not run. Never translate “looks plausible” or static inspection into “tested in Studio.”
What ships with it
2 files 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 Changed · +7 lines d49e1a1e075e
- 1mo ago Changed · +33 lines 77aa202a7285
- 1mo ago First seen · 144 lines · 96 tokens per session scan A e6b865515bb8
roblox-studio-workflow is a skill published in the GitHub repository gamedev-skills/awesome-gamedev-agent-skills (4,867 stars, last pushed 3d ago), licensed Apache-2.0. It adds 96 tokens to every session and 2,379 once invoked, about $0.0004 per session on Opus 5.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-09.
Other skills, from other repositories
tests-run
Execute Unity tests (EditMode or PlayMode) and return per-test results. Supports filtering by test assembly, namespace, class, and method. Refreshes the AssetDatabase first; defers execution across domain reloads if scripts changed. Precondition: every open scene must be saved — dirty scenes abort the run.
unity-pipeline
Drive a running Unity Editor or development Player from the command line via the unity-pipeline package — install the package, keep the editor ticking while unfocused, run the edit→recompile→runtests loop, evaluate C#, and hot-reload files at runtime. Use when an agent needs to control a live Unity instance, automate…
unity-agent-workflows
Use for AI-assisted Unity work that needs live repo discovery, project-derived routing, runtime-owner proof, runtime-visible output hard stops, runtime numeric proof for repeated visible-output failures, state-step guards, multi-agent scope ownership, modular C#/asmdef safety, UI/scene/visual asset gates, data-first…
testing-bgs-modpack
A checklist and decision guide for checking a newly installed batch of Bethesda Game Studios game modifications before accepting it as ready.
godot-testing
Use when writing tests for Godot projects — TDD workflow with GUT and gdUnit4, covers both GDScript and C#.
unity-cli
A command-line tool for checking and operating a Unity project, including its open scenes, game objects, assets, tests, compilation, and build checks. Unity is a game engine and editor.