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 batihandev/unity-mcp-skills --skill xrgit clone --depth 1 https://github.com/batihandev/unity-mcp-skillsWrote 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/batihandev/unity-mcp-skills/xr)<a href="https://agentmods.dev/skills/batihandev/unity-mcp-skills/xr"><img src="https://agentmods.dev/badge/skills/batihandev/unity-mcp-skills/xr/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/batihandev/unity-mcp-skills/xr"><img src="https://agentmods.dev/badge/skills/batihandev/unity-mcp-skills/xr.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.00051 | $0.01961 |
| Opus 5 | $0.00026 | $0.00981 |
| Sonnet 5 | $0.00010 | $0.00392 |
| Haiku 4.5 | $0.00005 | $0.00196 |
Grade A, and why
unity-xr 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity XR Interaction Toolkit Skills
Requirements
com.unity.xr.interaction.toolkit(≥ 3.4). Recipes target XRI 3 API only. If missing, install viaUnity_PackageManager_ExecuteActionwithoperation=Add,package=com.unity.xr.interaction.toolkit,version=3.4.1.
When to Use
Use this module for XR Interaction Toolkit setup and configuration.
Hard rule: Read this file before the first
xr_*call in a session. Wrong property names can fail silently because the bridge is reflection-based.
Common Mistakes
DO NOT (common hallucinations):
XRHand,XRPlayer,XRTeleporter,GrabInteractor,VRController,XRLocomotion, andXRManagerare not the runtime classes you want hereinteractable.OnGrab()/OnRelease()are not the XRI event model -> useselectEntered/selectExitedcontroller.vibrate()is not the documented route here -> configure haptics throughxr_configure_haptics- Do not assume physics Layer or Tag replaces
InteractionLayerMask - Do not guess component property names — they are set via reflection. Use the skill parameters directly
Correct class names to anchor on:
XRInteractionManagerXROriginXRRayInteractorXRDirectInteractorXRSocketInteractorXRGrabInteractableXRSimpleInteractableTeleportationProviderTeleportationAreaTeleportationAnchorContinuousMoveProviderSnapTurnProviderContinuousTurnProviderTrackedDeviceGraphicRaycasterXRUIInputModuleTrackedPoseDriver
Routing:
- For non-XR Canvas UI creation -> use
ui
Quick Reference
Setup and Diagnostics
| Skill | Use | Key parameters |
|---|---|---|
xr_check_setup |
Validate XR package, rig, managers, and scene prerequisites | verbose? |
xr_setup_rig |
Create XR Origin + camera + controllers | name, cameraYOffset? |
xr_setup_interaction_manager |
Add or find manager | none |
xr_setup_event_system |
Replace/add XR UI input stack | none |
xr_get_scene_report |
Report scene-side XR status | none |
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 · 176 lines · 51 tokens per session scan A 71a0ef7d166a
unity-xr is a skill published in the GitHub repository batihandev/unity-mcp-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,961 once invoked, about $0.0003 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
hz-unity-meta-movement-sdk-retargeting
Set up and tweak Meta Movement SDK (MSDK) retargeting for a character model. Use this whenever the user wants to retarget a humanoid FBX/prefab for Meta Quest body tracking, generate a retargeting config, or hand-edit the resulting .json (fix known-joint mappings, exclude joints from auto-mapping, rename target…
hz-unity-face-tracking
Drive ARKit-blendshape-rigged head/face models in Unity with the wearer's facial expressions on Meta Quest via Meta Movement SDK (face tracking + A2E). Use when a user has an FBX with the 52 ARKit blendshapes (any prefix, L/R suffixes) and wants it to animate from face tracking on Quest Pro / Quest 3 / Quest 3S.
hz-unity-meta-core-sdk
Meta XR Core SDK (com.meta.xr.sdk.core) for Unity XR development. Use when setting up VR/MR projects, configuring OVRManager, adding OVRCameraRig, enabling passthrough, hand tracking, spatial anchors, boundaryless mode, controller input, Scene API, or any Meta Quest XR feature. Covers OVRProjectSetup, AndroidManifest…
metavr-cli
Provides the complete metavr (Meta VR CLI) reference for Meta Quest and Horizon OS development — installation, device setup, command discovery, MCP server mode, documentation search, app deployment, device testing setup, audio control, screenshots, and performance analysis. Use when the user needs to install metavr…
hz-unity-passthrough-camera-access
Meta Quest Passthrough Camera Access (PCA) for Unity — access the forward-facing RGB cameras on Quest 3 / Quest 3S to feed Computer Vision and Machine Learning pipelines. Use when capturing the passthrough camera image/texture, reading the camera pose and intrinsics, projecting camera pixels into world space via…
animation-motion-capture
Implement motion capture integration and real-time synchronization.