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 3d-lightinggit 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/3d-lighting)<a href="https://agentmods.dev/skills/ouzlifaneyassine1-dot/onyx-engine/3d-lighting"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/3d-lighting/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/3d-lighting"><img src="https://agentmods.dev/badge/skills/ouzlifaneyassine1-dot/onyx-engine/3d-lighting.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.00086 | $0.01516 |
| Opus 5 | $0.00043 | $0.00758 |
| Sonnet 5 | $0.00017 | $0.00303 |
| Haiku 4.5 | $0.00009 | $0.00152 |
Grade A, and why
3d-lighting 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3D Lighting for Onyx Engine
Set up lighting and environment for 3D scenes. Follow these patterns for outdoor and indoor setups.
Light Types
| Type | Use case |
|---|---|
| DirectionalLight3D | Sun, moon, outdoor primary light |
| OmniLight3D | Point lights (lamps, torches) |
| SpotLight3D | Flashlights, stage lights |
Basic Outdoor Setup
1. Directional Light (Sun)
onyx_add_node(parent="./World", type="DirectionalLight3D", name="Sun")
onyx_set_prop(path="./World/Sun", key="rotation_degrees", value="Vector3(-45, 30, 0)")
onyx_set_prop(path="./World/Sun", key="light_energy", value="1.0")
onyx_set_prop(path="./World/Sun", key="shadow_enabled", value="true")
onyx_set_prop(path="./World/Sun", key="light_color", value="Color(1, 0.95, 0.9, 1)")
Warm sunlight: Color(1, 0.95, 0.9, 1). Cool moonlight: Color(0.8, 0.85, 1, 1).
2. WorldEnvironment (Sky + Ambient)
onyx_add_node(parent="./World", type="WorldEnvironment", name="WorldEnvironment")
onyx_set_prop(path="./World/WorldEnvironment", key="environment", value="Environment")
Then configure the Environment's sub-properties. The Environment resource has:
background_mode— 2 for sky, 1 for color, 3 for canvassky— Sky resource (ProceduralSkyMaterial or PhysicalSkyMaterial)ambient_light_source— AMBIENT_SOURCE_SKY or AMBIENT_SOURCE_COLORambient_light_colortonemap_mode
For a simple procedural sky:
onyx_set_resource_property(nodePath="./World/WorldEnvironment", resourceProperty="environment", subProperty="background_mode", value="2")
You may need to create a Sky resource and assign it. In the editor this is done via the inspector; via MCP, SetResourceProperty on nested resources may require the resource to exist first. If environment is "Environment", the engine creates a default. For sky, you might set sky to "ProceduralSkyMaterial" or similar—check Godot docs for the exact property chain.
Simpler path: Use the 3d-basic template which already has a sky. Copy that structure.
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 · 125 lines · 86 tokens per session scan A 817efebb3f6d
3d-lighting is a skill published in the GitHub repository ouzlifaneyassine1-dot/onyx-engine (0 stars, last pushed 2mo ago), licensed MIT. It adds 86 tokens to every session and 1,516 once invoked, about $0.0004 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
art-direction
Use when defining the visual style of the game — references, palette, mood, lighting plan, post-processing, do/don't list. Outputs an art bible at .summer/art-bible.md. Trigger on "art direction", "art bible", "visual style", "color palette", "what should it look like", "the look".
3d-lighting
Use when setting up lighting in a Summer Engine 3D scene — adding lights, configuring WorldEnvironment, sky, or shadows. Covers DirectionalLight3D versus Omni versus Spot, shadow tuning, ambient and sky-driven lighting, and the current Summer rendering conventions. Trigger on "lighting", "shadows", "WorldEnvironment"…
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
godot-signals-groups
Build event-driven, decoupled Godot 4.7 gameplay with signals and node groups: declare and emit custom signals, connect with Callables (incl. bind/one-shot), and broadcast to many nodes via groups and callgroup. Use when wiring node communication in a Godot project, replacing tight references with signals…
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).