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 german-krasnikov/unity-biome-mcp --skill unity-scene-authoringgit clone --depth 1 https://github.com/german-krasnikov/unity-biome-mcpWrote 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/german-krasnikov/unity-biome-mcp/unity-scene-authoring)<a href="https://agentmods.dev/skills/german-krasnikov/unity-biome-mcp/unity-scene-authoring"><img src="https://agentmods.dev/badge/skills/german-krasnikov/unity-biome-mcp/unity-scene-authoring/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/german-krasnikov/unity-biome-mcp/unity-scene-authoring"><img src="https://agentmods.dev/badge/skills/german-krasnikov/unity-biome-mcp/unity-scene-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 9 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00031 | $0.01079 |
| Opus 5 | $0.00015 | $0.00540 |
| Sonnet 5 | $0.00006 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
unity-scene-authoring 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Scene Authoring
If it is not already loaded, read
.claude/skills/unity-mcp-operations/SKILL.md once. Enable SCENE or
COMPONENTS only when a required tool is gated.
Workflow
- Read a hierarchy summary, then inspect only the target subtree.
- Resolve ambiguous names to exact hierarchy paths.
- Mark the console.
- Use one aggregate operation where possible.
- Read back changed components and validate references.
- Check the console delta and save the scene.
Scene Lifecycle And Environment
scene(action="list")
scene(action="open_additive", path="Assets/Scenes/Lighting.unity")
scene(action="set_active", path="Assets/Scenes/Lighting.unity")
scene_environment(action="get")
scene_environment(action="set", prop="fog", value="true")
scene_environment(action="set", prop="fogDensity", value="0.1")
Use explicit scene paths in multi-scene work. Inspect the live tool schema
before transferring objects between scenes, and save or discard each loaded
scene deliberately. scene_environment manages fog, skybox, and ambient
lighting settings.
Canonical Operations
setup_objects(specs="""
Marker primitive=Sphere parent=/Environment pos=(0,1,0)
Anchor parent=/Environment pos=(2,0,0)
""")
configure_objects(config="""
/Environment/Marker Transform.m_LocalScale=(0.25,0.25,0.25)
/Environment/Anchor Transform.m_LocalPosition=(2,0,0)
""")
Both are standalone typed tools. Their arguments are multiline strings named
specs and config.
Component lifecycle supports manage_component(action="add"|"remove").
To enable or disable a component, set its serialized enabled field after
confirming the property name with get_component.
manage_component(path="/Lamp", type="Light", action="add")
set_property(
path="/Lamp",
component="Light",
prop="m_Enabled",
value="false"
)
Use ping_object(path="/Target") to highlight and select an object in the
Editor hierarchy. Use get_selection() to read the currently selected object.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 150 lines · 31 tokens per session scan A 8cdf40635381
unity-scene-authoring is a skill published in the GitHub repository german-krasnikov/unity-biome-mcp (29 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 1,079 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
threejs-fundamentals
Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
threejs-geometry
Three.js geometry creation - built-in shapes, BufferGeometry, custom geometry, instancing. Use when creating 3D shapes, working with vertices, building custom meshes, or optimizing with instanced rendering.
threejs-world-generation
Build deterministic, editable, free-viewpoint Three.js worlds from text or structured briefs. Use for cinematic 3D terrain, semantic regions, procedural biomes, explicit landmarks, environmental scattering, camera fly-throughs, world diagnostics, or requests for a real 3D environment rather than generated 2D footage.…
sound-effects
Generate sound effects from text descriptions using ElevenLabs. Use when creating sound effects, generating audio textures, producing ambient sounds, cinematic impacts, UI sounds, or any audio that isn't speech. Supports looping, duration control, and prompt influence tuning.
character-animation-qa
Review local character animation with schema checks, Playwright browser previews, frame sampling, and FFmpeg/ffprobe final output checks.
pose-library-design
Design reusable 2D character pose libraries, action cycles, and expression states for data-driven animation.