game-development

game-development is a skill for Claude Code, Codex from metaspartan/cybara. It costs 49 tokens per session (606 once invoked), scanned A, original, MIT.

A routing guide for game-development work across major game engines, browser game frameworks, assets, interfaces, networking, and playtesting.

In plain words
What is it for?
Use it to start work on a game project, identify the engine and project constraints, and select workflows for implementation, assets, UI, networking, and testing.
Why use it?
It helps an agent choose the right engine-specific workflow and supporting skills when a game task covers several areas or the engine is not yet known.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to start work on a game project, identify the engine and project constraints, and select workflows for implementation, assets, UI, networking, and testing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/metaspartan/cybara/game-development
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 metaspartan/cybara --skill game-development
Clone the repo
git clone --depth 1 https://github.com/metaspartan/cybara

Made for: Claude Code, Codex.

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.

agentmods badge for game-development

README.md
[![agentmods](https://agentmods.dev/badge/skills/metaspartan/cybara/game-development/github.svg)](https://agentmods.dev/skills/metaspartan/cybara/game-development)
Your own site
<a href="https://agentmods.dev/skills/metaspartan/cybara/game-development"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/game-development/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.

agentmods 80×15 button for game-development

Your own site · 80×15
<a href="https://agentmods.dev/skills/metaspartan/cybara/game-development"><img src="https://agentmods.dev/badge/skills/metaspartan/cybara/game-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 606 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00049 $0.00606
Opus 5 $0.00024 $0.00303
Sonnet 5 $0.00010 $0.00121
Haiku 4.5 $0.00005 $0.00061

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

Security

Grade A, and why

game-development 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 9d 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.

plugins/game-development/skills/game-development/SKILL.md · 51 lines

How it starts

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

Game development

Use this skill as the entry point for game work that is not already scoped to one specialist workflow.

Routing

  1. Inspect project markers using ../../references/engine-workflows.md.
  2. Load exactly one primary engine skill:
    • Unreal Engine: ../unreal-engine/SKILL.md
    • Unity: ../unity/SKILL.md
    • Godot: ../godot/SKILL.md
    • Bevy: ../bevy/SKILL.md
    • Phaser, Three.js, React Three Fiber, Babylon.js, or PlayCanvas: ../web-game-development/SKILL.md
  3. Add ../game-asset-pipeline/SKILL.md when the task changes models, textures, animation, audio, or import settings.
  4. Add ../game-ui/SKILL.md for HUD, menus, input prompts, accessibility, and responsive layout.
  5. Add ../sprite-pipeline/SKILL.md for sprite sheets, atlases, pivots, animation frames, and engine imports.
  6. Add ../game-networking/SKILL.md for authoritative multiplayer, replication, prediction, rollback, lobbies, and network testing.
  7. Finish implementation work with ../game-playtesting/SKILL.md.
  8. Use the separate blender-mcp skill when a connected Blender workflow is needed.

Workflow

  1. Establish the engine version, target platforms, player verbs, and expected frame rate.
  2. Read repository instructions and the existing build and test setup.
  3. Separate simulation, presentation, input, UI, persistence, and platform integration.
  4. Make the smallest coherent change that follows the project's established architecture.
  5. Run engine-native validation before launching the game.
  6. Exercise the changed behavior through a representative player flow.
  7. Capture visual and performance evidence when those outcomes are in scope.

Guardrails

  • Do not upgrade an engine, renderer, render pipeline, scripting backend, or asset format unless requested.
  • Do not edit engine caches, generated project files, imported libraries, or binary assets as source.
  • Do not replace a working architecture with a generic template.
  • Do not call a game tested when only compilation or a static scene inspection ran.
  • Keep credentials, signing material, store keys, and proprietary platform SDK data out of output and logs.

Read the full file on GitHub · 51 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.

  1. 9d ago First seen · 51 lines · 49 tokens per session scan A 1c494d304b3b

Subscribe to this mod's changes

game-development is a skill published in the GitHub repository metaspartan/cybara (30 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 606 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.