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-vr-debuggit 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-vr-debug)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-vr-debug"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-vr-debug/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-vr-debug"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-vr-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
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 →
- high Anti-Refusal · line 35 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
- high Tool Misuse · line 108 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium MCP Rug Pull · line 31 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 33 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00069 | $0.04258 |
| Opus 5.5 | $0.00028 | $0.01703 |
| Sonnet 5.5 | $0.00014 | $0.00852 |
| Haiku 4.5 | $0.00007 | $0.00426 |
Grade A, and why
hz-vr-debug 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 25d 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 — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VR Debug Skill
Debug Meta VR, MR, and Android applications using the metavr command-line
interface. This skill covers viewing application logs, capturing device state,
diagnosing crashes, and resolving common issues encountered during Meta VR
development.
When to Use This Skill
Use this skill when you need to:
- Debug an application running on a connected Meta VR device
- View real-time or historical application logs (logcat)
- Capture screenshots of the VR/MR view
- Diagnose application crashes, rendering glitches, or performance problems
- Investigate tracking, controller, audio, or permission issues
- Pull diagnostic files from the device for offline analysis
This skill is relevant for Meta VR Glasses and Meta Quest headsets (Quest 2, Quest 3, Quest 3S, Quest Pro) running Horizon OS.
Prerequisites
Before using this skill, ensure the following are in place:
- metavr CLI installed -- Install the standalone
metavrCLI binary on your PATH (see themetavr-cliskill), or invoke it on demand vianpxwith no install:
metavr wraps ADB and adds Meta VR-specific device management, log viewing, screenshot capture, and file management. Examples below use the baremetavr --versionmetavrcommand. Ifmetavris not on PATH, invoke the same CLI vianpx -y metavr <args>(published as the npm packagemetavr). - Meta VR device connected via USB -- Use a USB-C cable that supports data transfer (not charge-only).
- Developer mode enabled -- Developer mode must be turned on in the Meta Horizon app on your phone, under your headset's settings.
- ADB authorization accepted -- The first time you connect, you must put on the headset and accept the "Allow USB debugging" prompt.
Quick Start Workflow
The fastest way to begin debugging a Meta VR application:
# 1. Verify the device is connected and recognized
metavr device list
# 2. List applications currently installed
metavr app list
# 3. View live logs (most recent 100 lines)
metavr log
# 4. Capture a screenshot of the current VR view
metavr capture screenshot
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.
- 25d ago Changed · +9 lines · +23 tokens per session 4fe3f4c41e94
- 1mo ago First seen · 394 lines · 46 tokens per session scan A 677fb6712c63
hz-vr-debug is a skill published in the GitHub repository meta-quest/agentic-tools (223 stars, last pushed 25d ago), licensed Apache-2.0. It adds 69 tokens to every session and 4,258 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
gamedev-physics
Use when working with a game engine's physics — rigid bodies, colliders, collision layers and masks, character controllers, joints, forces versus impulses, raycasts and shapecasts, or when a simulation is unstable (tunnelling, jitter, missed overlaps). Covers the Godot, Unity and Unreal equivalents. NOT rendering or…
aibridge-code-index
Optional read-only AIBridge Code Index lightweight lookup for Unity C# declaration names. Use only when Root Rule declares Code Index enabled and this Skill is installed. Map declaration names to files or positions. Do not use for references, callers, implementations, derived types, diagnostics, comments, strings, or…
swallowtail
Use the complete Godot development loop from the swallowtail CLI: discover the live engine API, build and edit in the open editor, run and play the game, observe state, debug failures, fix them in place, and verify the result. Use when the task involves creating or modifying a Godot project, testing game behavior…
janitor-fix
Automatically fix skill problems (safe preview first). Also use with --prune to find and remove broken symlinks, empty directories, and orphaned skills. Trigger with '/janitor-fix'.
repro-first
Bug-fix mode that reproduces a bug in a failing test before changing any code. Entered with /repro-first.
aibridge-development-workflow
A development workflow guide for projects built with Unity, a game and interactive-app engine. It routes coding, asset changes, debugging, reviews, and validation through project-specific rules and checks.