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 scene-compositiongit 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/scene-composition)<a href="https://agentmods.dev/skills/ouzlifaneyassine1-dot/onyx-engine/scene-composition"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/scene-composition/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/scene-composition"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/scene-composition.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.00063 | $0.01936 |
| Opus 5 | $0.00032 | $0.00968 |
| Sonnet 5 | $0.00013 | $0.00387 |
| Haiku 4.5 | $0.00006 | $0.00194 |
Grade A, and why
scene-composition 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scene Composition for Onyx Engine
Organize scenes for clarity, reuse, and MCP compatibility. Follow these conventions when building levels, characters, and UI.
Node Hierarchy Conventions
3D Scenes
World (Node3D) # Root or main container
├── Camera3D # Main camera
├── DirectionalLight3D # Sun / primary light
├── WorldEnvironment # Sky, ambient, fog
├── Level (Node3D) # Level geometry
│ ├── Ground
│ ├── Walls
│ └── Platforms
├── Props (Node3D) # Placed objects (trees, crates)
├── Enemies (Node3D) # Enemy instances
└── Player # Player instance (or instantiated)
2D Scenes
Level (Node2D)
├── TileMapLayer # Or TileMap
├── Characters
├── Props
└── Effects
UI Scenes
CanvasLayer or Control
├── MarginContainer
│ ├── VBoxContainer
│ │ ├── Label
│ │ ├── Button
│ │ └── Button
Parent Paths for MCP
Use ./ for paths relative to the scene root:
| Path | Meaning |
|---|---|
./ |
Scene root |
./World |
Child named "World" of root |
./World/Player |
Player under World |
./World/Props/Tree1 |
Tree1 under Props under World |
Never use /World (absolute) or World (missing ./). The engine expects ./ prefix.
When to Use Sub-Scenes
Use sub-scenes (separate .tscn files) when:
- The same setup appears in multiple places (player, enemy, pickup)
- The setup has many nodes and would clutter the main scene
- You want to edit a prefab in isolation
Use inline nodes when:
- The node is unique to this scene (main camera, level-specific light)
- It's a simple one-off (single MeshInstance3D)
Creating a Sub-Scene
- Build the hierarchy in the main scene
- Select the root of what you want to extract
- Save as scene:
onyx_save_scene(path="res://scenes/player.tscn"). SaveScene saves the current open scene, so build reusable scenes in their own open scene and save them there. Do not handwrite.tscnfiles as the preferred path. - In the main scene, add it with
onyx_instantiate_scene(parent="./World", scene="res://scenes/player.tscn", name="Player")
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 · 147 lines · 63 tokens per session scan A 51f86d8b7550
scene-composition is a skill published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 1,936 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 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.