Borrowing it
Nothing to install: this file belongs to oframe/ogpu. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/oframe/ogpu/main/.claude/skills/webgpu-utils-lookup/SKILL.mdgit clone --depth 1 https://github.com/oframe/ogpuWrote 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/oframe/ogpu/webgpu-utils-lookup)<a href="https://agentmods.dev/skills/oframe/ogpu/webgpu-utils-lookup"><img src="https://agentmods.dev/badge/skills/oframe/ogpu/webgpu-utils-lookup/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/oframe/ogpu/webgpu-utils-lookup"><img src="https://agentmods.dev/badge/skills/oframe/ogpu/webgpu-utils-lookup.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.00193 | $0.02071 |
| Opus 5.5 | $0.00077 | $0.00828 |
| Sonnet 5.5 | $0.00039 | $0.00414 |
| Haiku 4.5 | $0.00019 | $0.00207 |
Grade A, and why
webgpu-utils-lookup 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 12d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Answer webgpu-utils questions from the source, not from memory
webgpu-utils is small but full of non-obvious behavior: functions that mutate a
passed-in view in place, reflection that keys uniforms by declared name, helpers
that silently pick a texture view dimension for you, options whose defaults
matter (mips, usage, viewDimension). Memory of "roughly how it works" is
exactly where wrong answers come from — a misremembered option name or a stale
signature compiles fine and then breaks at runtime with no error. The cost of
checking is a few seconds; the cost of guessing is a silent garbage texture or a
buffer written to the wrong offset. So check first.
This codebase pins webgpu-utils 2.1.1 exactly (dist/2.x; its parser,
a bundled wgsl_reflect snapshot, is part of the contract). The installed copy
is the ground truth for this project — prefer it over anything you recall or find
online, because online docs track latest and may have drifted.
Lookup order
-
Local types — authoritative for the installed version. The
.d.tsfiles carry full signatures, option-object shapes, defaults, and the doc-comments (often with usage examples). Read these first:node_modules/webgpu-utils/dist/2.x/<module>.d.tsreferences/api-map.mdmaps every exported symbol to its.d.tsmodule so you can jump straight to the right file. -
Local implementation — when behavior isn't clear from the type alone. Questions like "does it mutate the argument or return a copy?", "what does it default the format to?", "how does it decide cube vs 2d-array?" are answered by reading the compiled source:
node_modules/webgpu-utils/dist/2.x/webgpu-utils.module.jsIt's readable ES —
grep -n 'function <name>'to find the definition. -
GitHub repo — for rationale, latest source, history, issues. Use when the local copy doesn't settle it, when the user asks about a version newer than 2.1.1, or when "why does it do this" needs the original TypeScript / commit context: https://github.com/greggman/webgpu-utils (source under
src/, one file per module mirroring the.d.tsnames). Fetch with WebFetch.
What ships with it
2 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.
- 12d ago Changed · +41 lines · +15 tokens per session 52b03b36ba72
- 1mo ago First seen · 97 lines · 178 tokens per session scan A 35d1259b52dc
webgpu-utils-lookup is a skill published in the GitHub repository oframe/ogpu (163 stars, last pushed 3d ago), licensed Unlicense. It adds 193 tokens to every session and 2,071 once invoked, about $0.0008 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…