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-post-processingnpx skills add Impertio-Studio/Three.js-Claude-Skill-Package --skill threejs-impl-post-processinggit 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-post-processing)<a href="https://agentmods.dev/skills/impertio-studio/three.js-claude-skill-package/threejs-impl-post-processing"><img src="https://agentmods.dev/badge/skills/impertio-studio/three.js-claude-skill-package/threejs-impl-post-processing.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.02881 |
| Opus 5 | $0.00062 | $0.01440 |
| Sonnet 5 | $0.00025 | $0.00576 |
| Haiku 4.5 | $0.00012 | $0.00288 |
Grade A, and why
threejs-impl-post-processing 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.
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
threejs-impl-post-processing
Quick Reference
Architecture Overview
Three.js offers TWO incompatible post-processing systems. NEVER mix them.
| System | Package | Approach | Best For |
|---|---|---|---|
| Built-in EffectComposer | three/addons/postprocessing/ |
One shader pass per effect | Simple setups, custom ShaderPass |
| pmndrs/postprocessing | postprocessing (npm) |
Merges effects into single pass | Performance-critical, R3F apps |
| WebGPU PostProcessing | three/addons/tsl/display/ |
Node-based TSL graphs | WebGPU renderer only |
Standard Pipeline (Built-in EffectComposer)
import { EffectComposer } from 'three/addons/postprocessing/EffectComposer.js';
import { RenderPass } from 'three/addons/postprocessing/RenderPass.js';
import { OutputPass } from 'three/addons/postprocessing/OutputPass.js';
const composer = new EffectComposer( renderer );
composer.addPass( new RenderPass( scene, camera ) ); // ALWAYS first
// ... effect passes here ...
composer.addPass( new OutputPass() ); // ALWAYS last
function animate() {
composer.render(); // replaces renderer.render( scene, camera )
}
Pass Ordering Rules
RenderPassMUST be the FIRST pass -- it renders the scene to the internal buffer- Effect passes go in the MIDDLE in any order (bloom, SSAO, outline, etc.)
- Anti-aliasing passes (SMAA, FXAA) go AFTER effect passes
OutputPassMUST be the LAST pass -- it applies tone mapping and color space conversion- NEVER omit
OutputPass-- without it, colors appear washed out or incorrect
Critical Warnings
NEVER mix three/addons/postprocessing/EffectComposer with pmndrs/postprocessing EffectComposer. They use incompatible buffer formats and will produce rendering artifacts or crashes.
NEVER forget to call composer.setSize() on window resize. Failing to resize the composer causes blurry or misaligned effects.
NEVER call renderer.render( scene, camera ) when using EffectComposer. ALWAYS call composer.render() instead -- calling both renders the scene twice.
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.
- 3d ago First seen · 325 lines · 123 tokens per session scan A af7c998915f6
threejs-impl-post-processing 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 2,881 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.