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 agentmods add skills/oframe/ogpu/naga-setupnpx skills add oframe/ogpu --skill naga-setupgit clone --depth 1 https://github.com/oframe/ogpuWhat 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 | $0.00170 | $0.01868 |
| Opus 5 | $0.00085 | $0.00934 |
| Sonnet 5 | $0.00034 | $0.00374 |
| Haiku 4.5 | $0.00017 | $0.00187 |
Grade A, and why
naga-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 2d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
naga-setup
Wire a repo so every WGSL edit is compiled by naga immediately, and the whole
shader tree can be checked in one command. WGSL errors otherwise only surface in
the browser console after a reload — this collapses that loop to zero.
The thing to keep straight
A working setup is four artifacts, and they arrive by different routes:
| Artifact | Travels with a git clone? |
|
|---|---|---|
| Repo config | .claude/settings.json hook — runs naga after each Edit/Write of a .wgsl, exits 2 on failure so the compiler error blocks and gets fixed in the same turn |
yes |
scripts/validate-shaders.mjs + npm entry — batch check for CI or a refactor that touched many shaders; the hook only sees files an agent writes, the script sees all of them |
yes | |
| Local toolchain | naga binary |
no |
jq binary |
no |
So a fresh clone of an already-wired repo still has half a setup: a hook that
fires and does nothing, because naga isn't on the machine. That's why step 1 is
the toolchain and not the config. Check each artifact, install whichever are
missing, and when all four are present say so and stop — re-adding the hook just
duplicates it.
Steps
1. Check the local toolchain
naga --version
jq --version
Missing naga makes everything else inert, so fix it first — and offer to run the
install rather than just quoting it, since on a fresh clone this is usually the
only gap:
brew install naga-cli # macOS / Linux — NOT `brew install naga`, that formula
# is a Snake game and collides on the same binary name
cargo install naga-cli # any platform with Rust
If naga --version succeeds but prints something that isn't a wgpu version
string, that's the Snake game — people hit this often enough to be worth checking
rather than assuming a zero exit means the compiler.
jq reads the tool payload for the hook. Usually present on macOS; brew install jq
otherwise.
2. Install the hook
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.
- 2d ago First seen · 165 lines · 0 tokens per session scan A e71f0c468c75
naga-setup is a skill published in the GitHub repository oframe/ogpu (139 stars, last pushed 21d ago), licensed Unlicense. It adds 170 tokens to every session and 1,868 once invoked, about $0.0009 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
geometry-and-math
Use this skill when using Phaser 4 math and geometry utilities. Covers vectors, rectangles, circles, triangles, polygons, random number generation, angles, distance, interpolation, and snapping. Triggers on: Vector2, Rectangle, Circle, math, distance, angle, random, lerp.
text-and-bitmaptext
Use this skill when displaying text in Phaser 4. Covers Text game objects, BitmapText, web fonts, text styling, word wrap, alignment, padding, and dynamic text content. Triggers on: Text, BitmapText, this.add.text, font, word wrap, text style.
unity-mcp-orchestrator
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for…
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
assets-prefab-save
Save the currently opened prefab edit stage back to its prefab asset without exiting the stage. Pair with 'assets-prefab-open' to enter the edit mode first.
mobile-games
Mobile game development principles. Touch input, battery, performance, app stores.