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 meta-quest/agentic-tools --skill hz-xr-simulator-setupgit clone --depth 1 https://github.com/meta-quest/agentic-toolsWrote 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/meta-quest/agentic-tools/hz-xr-simulator-setup)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-xr-simulator-setup"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-xr-simulator-setup.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.01543 |
| Opus 5 | $0.00019 | $0.00772 |
| Sonnet 5 | $0.00008 | $0.00309 |
| Haiku 4.5 | $0.00004 | $0.00154 |
Grade A, and why
hz-xr-simulator-setup 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 8d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Meta XR Simulator Setup
When to Use This Skill
- You need to test a Quest VR or MR application without a physical headset connected
- You want rapid iteration during development without deploying to device each time
- You are setting up CI/CD pipelines that need automated testing of Quest apps
- You want to validate core interactions, UI, and locomotion before deploying to hardware
What is Meta XR Simulator
Meta XR Simulator is a desktop tool that simulates a Meta Quest environment on your development machine. It intercepts the OpenXR runtime calls your application makes and provides simulated headset tracking, controller input, hand tracking, and environment data, allowing you to run and test VR/MR applications directly in your engine's editor or as standalone desktop builds.
The simulator does not replicate Quest hardware performance. It runs on your desktop GPU and CPU. Its purpose is functional testing, not performance profiling.
Supported Platforms
| Platform | Support Level |
|---|---|
| Windows 10/11 (64-bit) | Full support |
| macOS | Limited support |
Supported Engines
- Unity via Meta XR SDK (com.meta.xr.sdk.core and related packages)
- Unreal Engine via Meta XR Plugin (formerly Oculus VR Plugin)
Key Features
- Simulated headset tracking: Control head position and rotation with mouse and keyboard. Move through your virtual scene without wearing a headset.
- Simulated controller input: Map keyboard keys to Quest Touch controller buttons, thumbsticks, and triggers. Test interactions as if holding physical controllers.
- Simulated hand tracking: Trigger predefined hand poses and gesture sequences. Test pinch, grab, poke, and custom gestures without real hand tracking.
- Room setup and guardian simulation: Define a virtual play space with configurable room dimensions, furniture placement, and guardian boundaries. Test boundary-aware behavior.
- Passthrough simulation: Provide synthetic passthrough camera feeds for mixed reality application testing. Validate scene understanding and plane detection logic.
- Scriptable testing scenarios: Automate input sequences, record and replay sessions, and integrate with CI/CD for regression testing.
What ships with it
3 files 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.
- 8d ago First seen · 106 lines · 39 tokens per session scan A b85d49ece54e
hz-xr-simulator-setup is a skill published in the GitHub repository meta-quest/agentic-tools (190 stars, last pushed 17d ago), licensed Apache-2.0. It adds 39 tokens to every session and 1,543 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
skillshare-implement-feature
Implement a feature from a spec file or description using TDD workflow. Use this skill whenever the user asks to: add a new CLI command, implement a feature from a spec, build new functionality, add a flag, create a new internal package, or write Go code for skillshare. This skill enforces test-first development…
skillshare-cli-e2e-test
Run isolated E2E tests in devcontainer from aidocs/tests runbooks. Use this skill whenever the user asks to: run an E2E test, execute a test runbook, validate a feature end-to-end, create a new runbook, or test CLI behavior in isolation. If you need to run a multi-step CLI validation sequence (init → install → sync →…
evaluate-skill
Measure a skill's reliability — run it k times for a pass@k score, design or interpret its eval, or compare it against the base agent. Use when the user wants to run, design, or interpret a skill's eval, or write an .eval.yaml spec.
claude-code-smoke
Use when asked to run the Claude Code smoke evaluation.
grill-skill
Build and harden a skill with evals — interview to design its eval tasks, then run, measure, and iterate. Use when the user wants to create or improve a skill's eval, or run the create → test → improve loop for a skill.
cf-tdd
Use when writing new production code, adding features, implementing, or refactoring — e.g. "implement this", "build this feature", "create a function", "add a new endpoint", "write the implementation", "refactor this", "write a test", "add tests", "create a component", "implement the API", "add a route". Also…