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 new-projectgit 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/new-project)<a href="https://agentmods.dev/skills/ouzlifaneyassine1-dot/onyx-engine/new-project"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/new-project/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/new-project"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/new-project.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.00077 | $0.01191 |
| Opus 5 | $0.00039 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00238 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
new-project 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 10d 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 new-project — 42 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/new-project — Scaffold a fresh empty project
When the user wants to start from a blank canvas — not a community template, not a built-in starter scene — this is the path.
When to use this skill
- "Let's start a new project."
- "I want to make a [game type] from scratch."
- "Blank project."
- "Empty project."
- "I don't want a template, just a blank starting point."
When NOT to use this skill
- "Show me templates" / "use a template" →
onyx:browse-templates. - "Make me a game" with a defined idea → run
onyx:brainstorm-gamefirst to scope, then come back here once the user knows what they want. - "I have an existing Godot project I want to import" → not this skill; have the user run
onyx open <path>directly.
Steps
1. Ask the project name
One question, no menu:
"What do you want to call your project?"
Default: my-game. If they say "anything is fine" or similar, use my-game and move on. The directory name is reversible — they can always rename.
2. Pick the starting scene
Two built-in options:
empty— rootNode3Donly. Pure blank canvas. Best for: experimentation, when the user knows exactly what they want to build.3d-basic— rootNode3DwithCamera3D,DirectionalLight3D, a floorMeshInstance3D, and aWorldEnvironment. Best for: first-time users, when "just give me something I can press play on" is the vibe.
If you're not sure which fits, ask:
"Empty (just a root node) or 3d-basic (camera, light, and a floor — you can press play immediately)?"
If the user has clearly invoked onyx:brainstorm-game already and the brief calls for 3D, default to 3d-basic and mention you did. If 2D, use empty (we don't ship a 2D-basic yet).
3. Create
onyx create empty my-game
or
onyx create 3d-basic my-game
The command writes project.godot and the chosen main.tscn. No network call, fast, deterministic.
4. Open it
onyx run my-game
Confirm the engine launched and the project loaded. If onyx run fails, run onyx doctor and surface the failure to the user.
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.
- 10d ago First seen · 107 lines · 77 tokens per session scan A 2b3486fd244d
new-project is a skill published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It adds 77 tokens to every session and 1,191 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to new-project, differing in 42 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.