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/random6913/claude-code-superkit/threejs-color-managementnpx skills add RaNDoM6913/claude-code-superkit --skill threejs-color-managementgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/threejs-color-management)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/threejs-color-management"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/threejs-color-management.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.00055 | $0.00824 |
| Opus 5 | $0.00028 | $0.00412 |
| Sonnet 5 | $0.00011 | $0.00165 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
threejs-color-management 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 yesterday.
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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Three.js Color Management
Complete guide to the Three.js color pipeline. Use this when colors look wrong in 3D scenes — too bright, too dark, washed out, or distorted.
The Color Pipeline
Texture → Material → Renderer (toneMapping) → Output (outputColorSpace)
Every texture goes through this pipeline. Understanding each stage prevents color issues.
Stage 1: Texture colorSpace
Set on load. Tells Three.js how to interpret the texture data.
| Type | colorSpace | When |
|---|---|---|
| Photos, UI screenshots | THREE.SRGBColorSpace |
Colors created for human eyes |
| Normal maps, roughness | THREE.LinearSRGBColorSpace |
Data textures (not visual) |
| HDR environment | THREE.LinearSRGBColorSpace |
Already in linear space |
const texture = useTexture('/screen.png');
texture.colorSpace = THREE.SRGBColorSpace; // UI screenshot
Stage 2: Material toneMapped
Controls whether the material goes through the renderer's tone mapping.
| Scenario | toneMapped | Why |
|---|---|---|
| UI on 3D screen | false |
Preserve exact pixel colors |
| Realistic objects | true (default) |
HDR → SDR compression needed |
| Emissive displays | false |
Screens emit, don't reflect |
<meshBasicMaterial map={texture} toneMapped={false} />
Stage 3: Renderer toneMapping
Global setting. Compresses HDR values into displayable range.
| Value | Effect | Use when |
|---|---|---|
THREE.ACESFilmicToneMapping |
Cinematic, saturated | Realistic 3D scenes (default) |
THREE.NoToneMapping (0) |
No compression | UI textures are primary visual |
THREE.ReinhardToneMapping |
Gentle compression | Bright scenes, less contrast |
<Canvas gl={{ toneMapping: THREE.NoToneMapping }}>
Stage 4: Output colorSpace
renderer.outputColorSpace = THREE.SRGBColorSpace (default). Rarely change this.
Common Issues & Fixes
Colors too bright / oversaturated
Cause: Tone mapping amplifying already-sRGB colors.
Fix: toneMapped={false} on the material, or toneMapping: 0 on Canvas.
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.
- yesterday First seen · 98 lines · 55 tokens per session scan A 21f7c92fb492
threejs-color-management is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 824 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
apm-triage-panel
Use this skill to triage one microsoft/apm issue selected by the daily sweep, the status/needs-triage fast path, or manual dispatch. Emit one synthesized comment with a decision, label set, exact milestone, and suggested next action.
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…