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/ukanwat/aaabench/shader-programmingnpx skills add ukanwat/aaabench --skill shader-programminggit clone --depth 1 https://github.com/ukanwat/aaabenchWhat 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.00095 | $0.01857 |
| Opus 5 | $0.00048 | $0.00928 |
| Sonnet 5 | $0.00019 | $0.00371 |
| Haiku 4.5 | $0.00010 | $0.00186 |
Grade A, and why
shader-programming 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 3d 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.
This is a copy
100% identical to shader-programming — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shader programming (cross-engine)
Shaders are small programs that run per vertex and per pixel on the GPU.
The concepts — the pipeline, coordinate spaces, UVs, and how common effects are
built — port across engines; only the language dialect and built-in variable
names change. This skill teaches those portable fundamentals in GLSL with HLSL
equivalents; use godot-shaders (or Unity/Unreal material docs) for the exact
engine syntax and built-ins.
When to use
- Use to understand or write vertex/fragment shaders and to reason about UVs, coordinate spaces, and the GPU pipeline.
- Use to build common effects: tint/recolor, scrolling textures, dissolve, outlines, fresnel/rim light, vignette, color grading.
- Use to translate a shader concept between GLSL and HLSL, or between engines.
When not to use: for an engine's exact shader language and built-ins, use
godot-shaders (Godot shading language) or the engine's material docs. For full
particle VFX systems, see unreal-niagara. For post-process stacks, defer to
the engine's renderer settings.
Core workflow
- Know which stage you're in. The vertex shader transforms each vertex into clip space and passes data (UVs, normals) onward; the fragment/pixel shader runs per rasterized pixel and outputs a color. Most game effects live in the fragment stage.
- Track coordinate spaces. Positions move model → world → view → clip space; normals belong in world or view space. Mixing spaces is the most common bug.
- Drive effects with UVs and time. UVs are
0..1texture coordinates; offset, scale, or distort them, and animate with atimeuniform. - Work per pixel, branch-light. Prefer
mix,step,smoothstep, andclampoverifwhere possible; GPUs run pixels in lockstep and dislike divergent branches. - Pass data via uniforms (constant per draw) and varyings (interpolated vertex→fragment). Keep texture samples few; they dominate cost.
- Verify visually and on target hardware. Shaders that look right on desktop can break on mobile (precision, missing features). Test where it ships.
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.
- 3d ago First seen · 158 lines · 95 tokens per session scan A 5e8011dceb84
shader-programming is a skill published in the GitHub repository ukanwat/aaabench (378 stars, last pushed 19d ago), licensed MIT. It adds 95 tokens to every session and 1,857 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to shader-programming, differing in 6 lines, and is treated as a copy.
Other skills, from other repositories
unreal-pie
Domain skill - Unreal Engine Play-In-Editor (PIE) closed-loop verification. Provides PIE lifecycle control (enter/pause/resume/exit), controlled input injection (no OS dependency), viewport screenshot capture, output log snapshot, performance sampling, and Automation Test execution with async job polling. Use for…
unreal-playtest-agent
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
unreal-actors
Domain skill - Unreal Engine actor management: list, spawn, transform, and delete level actors. Use when inspecting or editing actors in the current Unreal Editor level. Not for Content Browser asset import/export - use unreal-assets for that.
unreal-cinematics
Domain skill — Sequencer shot and keyframe orchestration, camera cut tracks, and Movie Render Queue job setup. Use when creating or editing Level Sequences, authoring camera animation, or preparing an MRQ job in Unreal Engine 5. Not for Blueprint scripting (unreal-blueprints) or runtime playback (unreal-runtime).
unreal-fab-assets
Acquire free Fab marketplace content through Unreal Engine's official Fab integration, then verify the imported Content Browser assets. Use when the user asks to find, download, add, or import Fab or Unreal Marketplace assets. Not for arbitrary file imports - use unreal-assets instead.
unreal-metasound
Unreal Engine MetaSound Source authoring through the reflected Builder API: create sources, add typed inputs and exact registered nodes, connect opaque vertex handles, set defaults, inspect nodes, build, save, and validate. Use for procedural audio graphs in Unreal Engine 5.4+. Not for arbitrary asset management or…