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.
git clone --depth 1 https://github.com/AmaniDawn/DGameWrote 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/commands/amanidawn/dgame/baking)<a href="https://agentmods.dev/commands/amanidawn/dgame/baking"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/baking/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/commands/amanidawn/dgame/baking"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/baking.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.01469 |
| Opus 5.5 | $0.00000 | $0.00588 |
| Sonnet 5.5 | $0.00000 | $0.00294 |
| Haiku 4.5 | $0.00000 | $0.00147 |
Grade A, and why
baking 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 20d 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
100% identical to baking — 0 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Baking commands
Bake and clear precomputed scene data: lightmaps, NavMesh, and occlusion culling. Each bake_* runs asynchronously (returns immediately) — poll the matching *_bake_status until completed. The clear_* commands are destructive and require confirm=true. The get_*_settings / set_*_settings pairs read and tune the bake parameters.
Lighting
bake_lighting
Trigger an async lightmap bake of the open scene(s) via Lightmapping.BakeAsync(). Returns immediately; poll lighting_bake_status until completed.
| Parameter | Required | Default | Description |
|---|---|---|---|
confirm |
no | false |
Recommended (true): a bake overwrites existing lightmap data. Accepted for parity; not required. |
dry_run |
no | false |
If true, validate there is an open bakeable scene and return the current lighting settings without baking. |
Returns: object
lighting_bake_status
Get the status of the last lighting bake: idle | baking | completed.
Returns: string
cancel_lighting_bake
Cancel an in-progress lighting bake (Lightmapping.Cancel()).
Returns: object
clear_baked_lighting
Clear baked lightmap data for the open scene(s). Destructive: requires confirm=true.
| Parameter | Required | Default | Description |
|---|---|---|---|
confirm |
no | false |
Must be true to actually clear (destructive, not undoable via Unity's Undo). |
include_disk_cache |
no | false |
If true, also clear the GI disk cache (Lightmapping.ClearDiskCache()). |
dry_run |
no | false |
If true, report what would be cleared without clearing. |
Returns: object
get_lighting_settings
Read the active LightingSettings (lightmapper, bounces, resolution, directional mode, AO, etc.).
Returns: LightingSettingsResult
set_lighting_settings
Apply a subset of lighting settings to the active LightingSettings. Returns { applied[], unknown[] }.
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.
- 20d ago First seen · 141 lines · 0 tokens per session scan A 23aeea6d5ba4
baking is a command published in the GitHub repository AmaniDawn/DGame (173 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,469 tokens. A static security scan graded it A with 0 findings. It is 100% identical to baking, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
sim
Run the EmbodiedGen simulation rendering workflow with sim-cli.
cert-check
Review the current state against certification and platform compliance expectations.
combat-design
Design or revise combat rules, variables, readability, and tuning direction.
ui-flow-review
Review menus, HUD, navigation, and player flow from a UX perspective.
web-build-fix
Diagnose and resolve web build, bundling, or deployment issues.
tech-debt
Track and prioritize technical debt.