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/shadow-mappingnpx skills add oframe/ogpu --skill shadow-mappinggit 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.00104 | $0.01900 |
| Opus 5 | $0.00052 | $0.00950 |
| Sonnet 5 | $0.00021 | $0.00380 |
| Haiku 4.5 | $0.00010 | $0.00190 |
Grade A, and why
shadow-mapping 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fold shadow mapping into a RenderPipeline
The engine has no shadow primitive. Shadow mapping is two passes you wire by
hand: (1) a depth-only caster pass that renders the occluders from the
light's POV into a depth RenderTarget, and (2) receivers that sample that
depth map with a comparison sampler + PCF and darken their lighting. There is no
shader-chunk system — integration means copying the WGSL pieces into the target
shader and wiring the JS. This skill says which pieces and what breaks silently.
Two canonical, working implementations already in the repo — read the one that matches the geometry:
examples/shadowmapping/— static geometry (plain vertex attributes).shadow.wgslcaster,mesh.wgslreceiver. The minimal reference.examples/skinninggltf/— skinned + IBL character.shadowcaster.wgslpulls skinned positions from the Skin compute buffer so the cast shadow tracks the animation;skinnedmesh.wgslreceives (self-shadow),floor.wgslreceives (contact shadow). The reference for any compute/skinned/IBL case.
Decide the integration shape
- Static geometry (vertex attributes) → caster shader is a vertex-only
MVP * positionfrom the light camera. Copyexamples/shadowmapping/shadow.wgsl. - Skinned / compute-positioned / displaced geometry → the caster MUST pull
position the same way the main vertex stage does (same storage buffer, same
@builtin(vertex_index)indexing) or the shadow detaches from the animated mesh. Copyexamples/skinninggltf/shadowcaster.wgsl. - IBL-only / ambient-only shader (no punctual light) → there is nothing for
a shadow to occlude. Add a directional light gated by the shadow factor, or
the "shadow" does nothing visible. See
references/folding.md.
The JS wiring (depth target, light camera, caster mesh, shadow uniform,
comparison sampler, receiver bindings, two-pass render loop) is the same shape
in every case — references/folding.md has the copy-paste blocks.
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 · 118 lines · 104 tokens per session scan A feb643c69230
shadow-mapping is a skill published in the GitHub repository oframe/ogpu (138 stars, last pushed 21d ago), licensed Unlicense. It adds 104 tokens to every session and 1,900 once invoked, about $0.0005 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
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…