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 agentmods add skills/playcanvas/create-playcanvas/bake-lightingnpx skills add playcanvas/create-playcanvas --skill bake-lightinggit clone --depth 1 https://github.com/playcanvas/create-playcanvasWrote 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/playcanvas/create-playcanvas/bake-lighting)<a href="https://agentmods.dev/skills/playcanvas/create-playcanvas/bake-lighting"><img src="https://agentmods.dev/badge/skills/playcanvas/create-playcanvas/bake-lighting.svg" alt="Measured on agentmods" 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.00039 | $0.00764 |
| Opus 5 | $0.00019 | $0.00382 |
| Sonnet 5 | $0.00008 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00076 |
Grade A, and why
bake-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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- bake-lighting — 100% identical, 32 lines differ
How it starts
The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Precompute static lighting
Static geometry lit by static lights can bake into lightmap textures once, removing per-frame shadow-map rendering and per-pixel dynamic lighting for that light entirely.
Engine Lightmapper flags
- Engine-only bootstraps must register it:
AppOptions.lightmapper = Lightmapper.Applicationwires this by default; only a manualAppOptionsassembly needs the explicit line. - Per light:
light.bake = true, thenlight.affectDynamic = falseonce every mesh it lights is lightmapped, so it stops contributing to the real-time pass. - Per mesh:
render.lightmapped = true— required for the mesh to receive any light onceaffectDynamicis false, a correctness requirement, not just an optimization —render.lightmapSizeMultiplierto size its lightmap,render.castShadowsLightmapso lightmapped meshes still shadow each other in the bake. - Bake mode:
BAKE_COLORfor flat diffuse materials;BAKE_COLORDIRadds a dominant-light-direction pass for normal- or specular-mapped materials that need one. - Baked ambient occlusion, independent of any light:
scene.ambientBakeplusambientBakeNumSamples,ambientBakeOcclusionBrightness/OcclusionContrast. - Run
app.lightmapper.bake(null, mode)once the scene exists;nullbakes every lightmapped node.
Verify UVs before trusting this on real assets
Procedural primitives auto-generate a usable UV set; imported GLB models often do not ship a second,
non-overlapping UV channel suitable for a lightmap atlas. Read the installed engine's source for
what its Lightmapper actually requires — which UV set it samples, whether it unwraps one for you —
before assuming a real model will bake correctly. Do not carry a primitive-only test result into
production assets unchecked.
Choose the rung by budget, not by default
On-device bake cost scales with baked-node count and lightmap resolution; estimate it against the startup budget before choosing a rung. Stay on-device unless:
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.
- 6d ago First seen · 62 lines · 39 tokens per session scan A 8dec56ebc8c7
bake-lighting is a skill published in the GitHub repository playcanvas/create-playcanvas (53 stars, last pushed yesterday), licensed MIT. It adds 39 tokens to every session and 764 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-08-30.
Other skills, from other repositories
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).
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.
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…
threejs-exposure-color-grading
Build a measured exposure and grading path in Three.js. Use for a 64x36 encoded luminance meter, asynchronous readback, weighted log-average exposure, asymmetric adaptation, single tone-map ownership, and a generated 32-cube post-tone-map LUT.