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 skills add linegel/threejs-complete-set-of-skill --skill threejs-particles-trails-and-effectsgit clone --depth 1 https://github.com/linegel/threejs-complete-set-of-skillWrote 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/linegel/threejs-complete-set-of-skill/threejs-particles-trails-and-effects)<a href="https://agentmods.dev/skills/linegel/threejs-complete-set-of-skill/threejs-particles-trails-and-effects"><img src="https://agentmods.dev/badge/skills/linegel/threejs-complete-set-of-skill/threejs-particles-trails-and-effects/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/linegel/threejs-complete-set-of-skill/threejs-particles-trails-and-effects"><img src="https://agentmods.dev/badge/skills/linegel/threejs-complete-set-of-skill/threejs-particles-trails-and-effects.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00064 | $0.01997 |
| Opus 5 | $0.00032 | $0.00999 |
| Sonnet 5 | $0.00013 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
threejs-particles-trails-and-effects 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 12d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Representation-First Particles, Trails, and Effects
Own GPU-resident object- and world-space effects: spawn, motion, lifetime,
compaction, draw representation, depth/blend behavior, and scene-linear HDR
emission. Route viewport history to $threejs-dynamic-surface-effects, weather
accumulation to $threejs-rain-snow-and-wet-surfaces, authored event motion to
$threejs-procedural-motion-systems, and shared post ownership to
$threejs-image-pipeline or $threejs-bloom.
When an effect consumes collision, forcing, or exchange owned by another system, close this local handoff before step 1:
- name the quantity and units, producer frame/origin, transform revision, and origin generation;
- name the half-open source interval, cadence, sample phase, immutable producer version, and permitted pool consumer;
- declare support/filter, validity, staleness, error, and missing/overflow policy;
- mark one-way reads or name the two-way source/reaction owners, application order, and applied state version;
- bind the GPU resource generation, producing and consuming passes, completion dependency, and reset on discontinuity, rebase, or generation change while keeping the steady frame readback-free.
The source owner retains authority; the pool consumes immutable publications.
Invoke $threejs-choose-skills when the route needs additional system owners.
Then read coupled inputs
for effect-specific ownership and degradation rules.
Process
1. Define the observable and its owners
Write one effect contract containing:
- the event interval, deterministic seed, effect class, transform, and flow/impact direction;
- the coordinate frame, distance/time units, lifetime clock, and seek/reset behavior;
- the visible roles: silhouette, motion, illumination, residue, or occlusion;
- the depth-test, depth-write, blend/order, HDR signal, and final-output owner;
- any external producer and whether the pool is presentation-only or backed by a separately owned physical body.
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.
- 12d ago First seen · 180 lines · 64 tokens per session scan A a4a643bad061
threejs-particles-trails-and-effects is a skill published in the GitHub repository linegel/threejs-complete-set-of-skill (6 stars, last pushed 1mo ago), licensed ISC. It adds 64 tokens to every session and 1,997 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-08-31.
Other skills, from other repositories
p5js
Use when users request: p5.js sketches, creative coding, generative art, interactive visualizations, canvas animations, browser-based visual art, data viz, shader effects, or any p5.js project.
pretext
Build creative browser demos with DOM-free text layout.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
inspecting-hermes-desktop-dom
Read the live Hermes desktop DOM/CSS over CDP.
html-artifacts
Author the HTML for a plan artifact, dashboard iframe, or Slack attachment — structure, design plan, available runtime, theming, and craft. Read this before writing HTML for saveplan, outputiframe, or slackattachhtml.
langbot-dev
Develop, build, and debug the LangBot core backend and web frontend. Use when working inside the LangBot repository — backend (Python/Quart, src/langbot/pkg), the Vite/React web UI, HTTP API controllers/services, Alembic migrations, or the MCP server. Covers the dev environment (uv, pnpm), repo layout, the API auth…