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 ouzlifaneyassine1-dot/onyx-engine --skill make-gamegit clone --depth 1 https://github.com/ouzlifaneyassine1-dot/onyx-engineWrote 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/ouzlifaneyassine1-dot/onyx-engine/make-game)<a href="https://agentmods.dev/skills/ouzlifaneyassine1-dot/onyx-engine/make-game"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/make-game/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/ouzlifaneyassine1-dot/onyx-engine/make-game"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/make-game.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02699 |
| Opus 5 | $0.00000 | $0.01350 |
| Sonnet 5 | $0.00000 | $0.00540 |
| Haiku 4.5 | $0.00000 | $0.00270 |
Grade A, and why
make-game 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.
This is a copy
88% identical to make-game — 89 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/make-game — The orchestration spine
This is the skill that runs end-to-end when a user says "make me a game." It does not try to do everything itself. It runs the right specialist skills in the right order with explicit handoffs and a checkpoint between every phase.
Core principle: structure beats vibes. A guided pipeline that delegates to focused specialists produces a real game. Off-the-cuff "let me think about it" loops produce three half-finished prototypes. Follow the phases. Don't skip.
When to use this skill
- User says: "make me a game", "build me a game", "I want to make a [genre]", "let's build a game", "build me a [shape]".
- User has nothing yet and wants the full path from idea → playable.
- User has a vague idea and wants the agent to drive the whole arc.
When NOT to use this skill
- User has a specific narrow ask ("add jump", "fix this bug", "design the inventory") → use the specific skill, not this orchestrator.
- User already has a working scaffold and wants to iterate → start at the relevant phase below, don't re-run the whole pipeline.
- User says "I want to use a template" → run
onyx:browse-templatesfirst; come back here only if they decide they want a custom build instead.
The Pipeline
Brainstorm → Plan → Scaffold → Build → Layer → Polish → Verify → Ship
│ │ │ │ │ │ │ │
▼ ▼ ▼ ▼ ▼ ▼ ▼ ▼
brainstorm plan new-project build-loop art vfx play export
-game (this browse- (this skill) audio debug -and-
skill) templates ship
↓
(one mechanic at a time:
design-mechanic + scene-composition
+ gdscript-patterns + play check)
Run the phases in order. Between every phase, stop and confirm with the user before continuing. The user owns scope decisions; the agent owns execution discipline.
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.
- 9d ago First seen · 266 lines · 0 tokens per session scan A 9998d2bb2d48
make-game is a skill published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,699 tokens. A static security scan graded it A with 0 findings. It is 88% identical to make-game, differing in 89 lines, and is treated as a copy.
Other skills, from other repositories
make-game
Use when the user says "make me a game", "build me a game", "I want to make a [genre] game", "let's build something" — the orchestration spine that runs the full game-dev pipeline: brainstorm → plan → scaffold → build core mechanics → art direction → audio → polish/VFX → verify → ship. Delegates to specialist skills…
brainstorm-game
Use when the user wants help deciding what game to make, scoping a new project, or turning a vague idea into a buildable plan. Walks through genre, scope, core loop, mechanics, and art direction, then writes a 1-page brief to .summer/GameSoul.md. Trigger on "brainstorm a game", "what should I make", "I want to make a…
scene-composition
Use when building or organizing Summer Engine scenes: node hierarchy conventions, when to extract sub-scenes, reusable prefab patterns, and instance-versus-add-node decisions. Trigger on "scene", "sub-scene", "instance", "prefab", "node hierarchy", "scene structure", "PackedScene".
browse-templates
Use when the user wants to see available Summer Engine project templates, start from an existing template, or asks "what templates exist?" — fetches the live list from github.com/SummerEngine, presents the choices, and creates a project from the chosen template via summer create . Trigger on "templates", "starter"…
new-project
Use when the user wants a fresh blank Summer Engine project — not from a template. Asks one question (project name) and runs summer create empty . Trigger on "new project", "blank project", "empty project", "from scratch", "start fresh", "create new game", "blank canvas", "scaffold a project".
play
Use when the user says "play", "run it", "test it", "let me see it", or "start the game". Runs the project in Summer Engine, briefly waits, then reports what's happening — clean run, errors, or warnings.