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-unity-code-reviewgit 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-unity-code-review)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-unity-code-review"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-unity-code-review/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-unity-code-review"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-unity-code-review.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 MCP Rug Pull · line 206 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.00043 | $0.01893 |
| Opus 5.5 | $0.00017 | $0.00757 |
| Sonnet 5.5 | $0.00009 | $0.00379 |
| Haiku 4.5 | $0.00004 | $0.00189 |
Grade A, and why
hz-unity-code-review 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 1mo 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Code Review for Meta VR
When to Use
Use this skill when reviewing Unity C# code or project settings that target Meta VR headsets. This includes:
- Reviewing scripts for VR performance issues
- Checking rendering pipeline configuration and settings
- Ensuring adherence to Meta VR-specific best practices
- Identifying common VR development pitfalls
- Validating input handling for controllers, hands, and eye tracking
- Auditing memory usage and GC allocation patterns
Key Review Areas
1. Rendering Pipeline Configuration
Meta VR applications must use the Universal Render Pipeline (URP) with specific settings optimized for mobile VR. The Built-in Render Pipeline is not recommended for new Meta VR projects.
Critical settings to verify:
- Single-pass multiview must be enabled (Player Settings > XR Plug-in Management > Oculus > Stereo Rendering Mode)
- Vulkan should be the primary graphics API
- Linear color space is required for correct lighting
- HDR should be disabled in URP asset settings
- Post-processing should be minimal or disabled
2. Draw Call Budgets and Batching
Meta VR has draw call budgets that vary by workload complexity. Every draw call has CPU overhead that directly impacts frame timing.
| Metric | Quest 2 / Quest Pro | Quest 3 / Quest 3S | Meta VR Glasses |
|---|---|---|---|
| Draw calls (busy simulation) | 80-200 | 200-300 | 200-300 |
| Draw calls (medium simulation) | 200-300 | 400-600 | 400-600 |
| Draw calls (light simulation) | 400-600 | 700-1000 | 700-1000 |
| Triangles per frame | 750K-1M | 1M-2M | 1M-2M |
| SetPass calls | < 50 | < 80 | < 80 |
Enable and verify:
- Static batching for non-moving geometry
- GPU instancing for repeated objects
- SRP batcher for URP materials
- Dynamic batching for small meshes (< 300 vertices)
3. Shader Complexity
Mobile GPUs on Meta VR cannot handle desktop-class shaders. Review all materials for:
- Use of URP/Lit or URP/Simple Lit instead of Standard shader
- Custom shaders that minimize texture samples and ALU operations
- Avoidance of real-time shadows where possible (bake instead)
- No screen-space effects (SSAO, SSR, screen-space shadows)
What ships with it
4 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.
- 1mo ago Changed · +1 tokens per session db2f5a345d0f
- 1mo ago First seen · 233 lines · 42 tokens per session scan A b60fba1626d0
hz-unity-code-review is a skill published in the GitHub repository meta-quest/agentic-tools (236 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,893 once invoked, about $0.0002 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
skillshare-code-review
Review a skillshare change before it becomes a pull request, or review an open pull request. Use this skill whenever the user asks to: review a diff, branch, commit range or PR, check a change before opening a PR, run a pre-Codex review, or find what a change missed. It checks correctness, the repository's documented…
doris-repo-review
Review an Apache Doris PR from a local clone with the same multi-agent, shared-ledger convergence workflow as the CI Code Review Runner. Use when the user supplies a PR to /doris-repo-review, asks to review a Doris PR locally, or asks for the CI-style review flow. Safely align only the current worktree to the exact PR…
rules-code-immutability
The rules for the state of an object. Use when you write a new class, a new struct or a new record, when you write a constructor, when you add a property to a type that exists, when you write a setter or a method that writes a property of its own object, when a caller needs an object with one different value, when a…
rules-code-type-safety
The rules for the parameters, the properties and the return type of a signature. Use when you write a new method, a new function, a new class, a new constructor or a new property, when you add a parameter to a signature that exists, when you change what a method takes or what it returns, when you let a caller choose a…
rules-code-without-slop
The rules for the code that carries no evidence, which a reader names slop. Use when you write a new method or a new function, when you finish a change, when you read a request, a file, a document or a row of a database, when you check the type of a value in the middle of the program, when you write a try and a catch…
rules-code-public-api
The rules for the public API of a package and the visibility of each item. Use when you write a new type, a new method or a new constructor, when you change the visibility of a type or of a member, when a caller outside this project can reach a type or a member, when you add a parameter to a signature that a caller…