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/project-settings)<a href="https://agentmods.dev/commands/amanidawn/dgame/project-settings"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/project-settings/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/project-settings"><img src="https://agentmods.dev/badge/commands/amanidawn/dgame/project-settings.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.02564 |
| Opus 5.5 | $0.00000 | $0.01026 |
| Sonnet 5.5 | $0.00000 | $0.00513 |
| Haiku 4.5 | $0.00000 | $0.00256 |
Grade A, and why
project-settings 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 project-settings — 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project settings commands
Read and change a representative slice of Unity's project-wide settings (Audio, Graphics, Input, Physics, Player, Quality, Tags & Layers, Time). get_* commands read a group's current values into a ProjectSettingsResponse; set_* commands mutate them through the shared confirm/dry_run convention, so confirm=true is required to apply and dry_run=true previews the change without applying it. Every command in this group is MainThreadRequired = true. On a set_*, omitted fields are left unchanged, and the group is re-read after the write so the response reflects the resulting state. Settings writes are not undoable via Ctrl+Z.
get_audio_settings
Read project Audio settings (volume, rolloff scale, doppler factor).
No parameters.
Returns: ProjectSettingsResponse
Notes: MainThreadRequired = true.
set_audio_settings
Change project Audio settings. Requires confirm=true; use dry_run to preview.
| Parameter | Required | Default | Description |
|---|---|---|---|
settings |
no | – |
Fields to change; omitted fields are left unchanged (fields below). |
confirm |
no | false |
Apply the change. Without it the call is refused. |
dry_run |
no | false |
Preview the change without applying it. |
settings fields:
| Field | Required | Default | Description |
|---|---|---|---|
volume |
no | – |
Global audio volume (0..1). |
rolloffScale |
no | – |
Global rolloff scale. |
dopplerFactor |
no | – |
Global doppler factor. |
Returns: ProjectSettingsResponse
Notes: MainThreadRequired = true. confirm=true required to apply; supports dry_run.
get_graphics_settings
Read GraphicsSettings (default render pipeline).
No parameters.
Returns: ProjectSettingsResponse
Notes: MainThreadRequired = true.
set_graphics_settings
Set the default render pipeline asset. Requires confirm=true; use dry_run to preview.
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 · 240 lines · 0 tokens per session scan A cffdc0337837
project-settings 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 2,564 tokens. A static security scan graded it A with 0 findings. It is 100% identical to project-settings, 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.