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-controlgit 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-control)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-xr-simulator-control"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-xr-simulator-control/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/meta-quest/agentic-tools/hz-xr-simulator-control"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-xr-simulator-control.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.00135 | $0.02405 |
| Opus 5.5 | $0.00054 | $0.00962 |
| Sonnet 5.5 | $0.00027 | $0.00481 |
| Haiku 4.5 | $0.00014 | $0.00241 |
Grade A, and why
hz-xr-simulator-control 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 24d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XR Simulator Control
metavr is overwhelmingly a physical Quest or Glasses CLI: device, app, capture, input, log,
files and ui all talk to a headset over ADB. xrsim is one group among them and drives a
simulated headset instead. Choosing the wrong group is the most common failure here, and it
is quiet: metavr device list prints No devices connected and exits 0, so the wrong answer
looks healthier than the right one.
This skill drives a simulator that already exists. Installing one, or wiring it into a project,
belongs to hz-xr-simulator-install-and-configure.
Which Command Group
| The goal concerns | Use | Not |
|---|---|---|
| The simulated headset model, IPD, refresh rate | metavr xrsim device … |
metavr device … (physical, ADB) |
| The simulator frontend process | metavr xrsim app … |
metavr app … (APKs on a headset) |
| Simulated hands and controllers | metavr xrsim input … |
metavr input … (keyevents to hardware) |
| The simulator's synthetic room | metavr xrsim env … |
— |
| Compositor layers, simulated frame rate | metavr xrsim layer / xrsim runtime fps |
— |
| The simulator's own logs | metavr xrsim runtime logs |
metavr log / metavr adb logcat (device logcat) |
| What the simulated headset renders | metavr xrsim record |
metavr capture (physical device screen) |
| Recording and replaying an app's OpenXR calls on a real headset | metavr tapedeck |
metavr xrsim record (compositor pixels, not a call stream) |
| The SpatialSim emulator | metavr ssim |
metavr xrsim (a different simulator) |
Read the Use column as the right tool for that goal and Not as the one you might reach for by
mistake. The last two rows are in this table because they are the mistakes, not because they are
this skill's job.
Three are worth stating outright, because a plausible command exists on both sides:
- "Record an OpenXR session" is the most confusable intent in the CLI.
xrsim recordcaptures the simulator's compositor output to MP4;tapedeckcaptures and replays an app's OpenXR call stream on a physical device. They are not substitutes. - "The simulator" is ambiguous inside this binary.
ssimis the SpatialSim emulator,xrsimis the Meta XR Simulator. device,appandinputexist both at the top level and underxrsim, so the same verb means different things depending on the group.capturedoes not: there is noxrsim capture, and the simulator equivalent isxrsim record.
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.
- 24d ago First seen · 153 lines · 135 tokens per session scan A 2caa710ecfb7
hz-xr-simulator-control is a skill published in the GitHub repository meta-quest/agentic-tools (221 stars, last pushed 25d ago), licensed Apache-2.0. It adds 135 tokens to every session and 2,405 once invoked, about $0.0005 per session on Opus 5.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-09-25.
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-windows-utm
Verify skillshare on a real Windows guest running in local UTM: build a pinned commit in the devcontainer, push it into the VM, and either run the Windows E2E runbook with full and basic-user tokens or hand the maintainer a one-line hands-on setup. Use this whenever a change touches Windows links, junctions, file…
evaluate-skill
Run, read, and diagnose a skill's Caliper eval — its success rate over k attempts, whether it fires, and whether it beats the agent without it. Use when the user wants to run, validate, interpret, or compare a skill's eval, or write an .eval.yaml spec whose tasks they have already decided.
grill-skill
Interview the user to decide what a skill's eval should test, then build the spec and iterate until the skill ships. Use when the user wants help designing a skill's eval, has a skill with no eval, or wants to find what an existing eval misses.
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 →…
repro-first
Bug-fix mode that reproduces a bug in a failing test before changing any code. Entered with /repro-first.