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-project-analyzergit 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-project-analyzer)<a href="https://agentmods.dev/skills/meta-quest/agentic-tools/hz-unity-project-analyzer"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-unity-project-analyzer/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-project-analyzer"><img src="https://agentmods.dev/badge/skills/meta-quest/agentic-tools/hz-unity-project-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.02313 |
| Opus 5.5 | $0.00024 | $0.00925 |
| Sonnet 5.5 | $0.00012 | $0.00463 |
| Haiku 4.5 | $0.00006 | $0.00231 |
Grade A, and why
hz-unity-project-analyzer 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 29d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Project Analyzer
Analyze, document, and maintain a living knowledge base of a Unity project's structure, optimized for AI agent comprehension. Output lives in .agent-docs/ as source-control-friendly markdown files.
Modes of Operation
This skill operates in four modes. Determine which mode to use based on context:
Mode 1: First-Time Full Scan
Trigger: .agent-docs/ directory does not exist or .agent-docs/index.md does not exist.
Mode 2: Incremental Update
Trigger: User asks to update docs, or AI agent has made structural changes (new scenes, scripts, prefabs, systems). Default update mode.
Important: Incremental updates are part of implementation, not a separate step. When creating or modifying scripts, prefabs, or assets, update the corresponding .agent-docs/ files in the same pass before moving on to the next task.
Mode 3: Full Rescan
Trigger: User explicitly requests a full rescan (e.g., "rescan project", "full project analysis").
Mode 4: Ingestion
Trigger: User asks about the project structure or how a system/feature works (e.g., "what does this project do", "how does the ball system work", "project structure", "load project analysis"). Only use this mode when .agent-docs/ exists. This mode is read-only — do not modify docs.
Instructions for Full Scan (Mode 1) and Full Rescan (Mode 3)
Step 1: Gather Project Overview
- Read
README.md,CHANGELOG.md, and any docs inDocumentation/folder - Read
Packages/manifest.jsonto understand all included packages - List all scenes:
Assets/**/*.unity - List all script folders and assembly definitions:
Assets/**/*.asmdef - List all prefab folders: find directories containing
.prefabfiles - Identify the project's Unity version from
ProjectSettings/ProjectVersion.txt - If an Editor is reachable (
unity status --format jsonshows stateready), inspect it live for richer data than the files alone give —unity command get_scene_hierarchy,find_assets,package_list --scope installed, and theget_*_settingscommands (get_player_settings,get_quality_settings,get_graphics_settings). See theunity-cliskill. - If a headset is attached, record the test-device baseline —
metavr device listandmetavr device info <id>(OS version, form factor) — so later findings can cite the hardware they were observed on.
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.
- 29d ago Changed · +1 lines 6193f974f405
- 1mo ago First seen · 218 lines · 59 tokens per session scan A 5b77cfcd0d6b
hz-unity-project-analyzer is a skill published in the GitHub repository meta-quest/agentic-tools (231 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,313 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
generate-minecraft-3D-build-plan
Call Craftsman Agent API OneKey Router to generate a Minecraft 3D scene build plan.
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
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-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…
skillshare-update-docs
Update website docs to match recent code changes, cross-validating every flag against source. Use this skill whenever the user asks to: update documentation, sync docs with code, document a new flag or command, fix stale docs, or update the README. This skill covers all website/docs/ categories (commands, reference…
officecli-word-form
Use this skill to create fillable Word forms (.docx) with real Content Controls (SDT) + legacy FormField checkboxes + MERGEFIELD mail-merge placeholders + document protection. Trigger on: 'fillable form', 'form fields', 'content controls', 'SDT', 'word form', 'fill in', 'only editable fields', 'protect document'…