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/impertio-studio/three.js-claude-skill-package/threejs-impl-webgpunpx skills add Impertio-Studio/Three.js-Claude-Skill-Package --skill threejs-impl-webgpugit clone --depth 1 https://github.com/Impertio-Studio/Three.js-Claude-Skill-PackageWrote 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/impertio-studio/three.js-claude-skill-package/threejs-impl-webgpu)<a href="https://agentmods.dev/skills/impertio-studio/three.js-claude-skill-package/threejs-impl-webgpu"><img src="https://agentmods.dev/badge/skills/impertio-studio/three.js-claude-skill-package/threejs-impl-webgpu.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00123 | $0.03111 |
| Opus 5 | $0.00062 | $0.01555 |
| Sonnet 5 | $0.00025 | $0.00622 |
| Haiku 4.5 | $0.00012 | $0.00311 |
Grade A, and why
threejs-impl-webgpu 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 5d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
threejs-impl-webgpu
EXPERIMENTAL — The WebGPU renderer and TSL are under active development. API surfaces may change between Three.js releases. Pin your Three.js version.
Quick Reference
WebGPURenderer Setup
import * as THREE from 'three/webgpu';
const renderer = new THREE.WebGPURenderer({ antialias: true });
await renderer.init(); // MUST await before first render
renderer.setSize(window.innerWidth, window.innerHeight);
renderer.setAnimationLoop(animate);
document.body.appendChild(renderer.domElement);
ALWAYS call await renderer.init() before the first renderer.render() call.
ALWAYS use renderer.setAnimationLoop(callback) instead of requestAnimationFrame.
NEVER call renderer.render() before init() resolves — this throws a runtime error.
Browser Support
| Browser | Version | Status |
|---|---|---|
| Chrome | 113+ | Full support |
| Edge | 113+ | Full support |
| Safari | 18+ | Supported |
| Firefox | Experimental | Behind flag (dom.webgpu.enabled) |
Feature Detection and Fallback
import { WebGPU } from 'three/webgpu';
if (WebGPU.isAvailable()) {
const renderer = new THREE.WebGPURenderer({ antialias: true });
await renderer.init();
} else {
const renderer = new THREE.WebGLRenderer({ antialias: true });
}
ALWAYS check WebGPU.isAvailable() before creating a WebGPURenderer.
ALWAYS provide a WebGLRenderer fallback for unsupported browsers.
Critical Warnings
NEVER write raw GLSL or WGSL strings — ALWAYS use TSL functions. WebGPU compiles TSL to WGSL automatically. GLSL is NOT supported by the WebGPU backend.
NEVER use ShaderMaterial with WebGPURenderer — use NodeMaterial with TSL instead.
NEVER use requestAnimationFrame with WebGPURenderer — ALWAYS use renderer.setAnimationLoop().
NEVER use EffectComposer (three/examples) with WebGPURenderer — use the PostProcessing class with TSL nodes instead.
Node Materials
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.
- 5d ago First seen · 314 lines · 123 tokens per session scan A 964398938fcd
threejs-impl-webgpu is a skill published in the GitHub repository Impertio-Studio/Three.js-Claude-Skill-Package (11 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 3,111 once invoked, about $0.0006 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
implement
Implement a feature or fix with automatic validation.
python-style
Validate Python code against style and architectural conventions.
error-handling
Validate error handling completeness across languages.
go-effective
Validate Go code against Effective Go and idiomatic conventions.
go-proverbs
Validate Go code changes against Go Proverbs.
state-machine
Validate state machine and lifecycle correctness.