three-js

A Three.js coding rule requiring THREE.Vector3 calls to end with a closing parenthesis.

In plain words
What is it for?
It is for checking and fixing Three.js vector code while avoiding unsafe text-based edits and backup-file creation.
Why use it?
It helps prevent syntax errors caused by unfinished vector constructor calls.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/panozzaj/cursor-rules/three-js
Clone the repo
git clone --depth 1 https://github.com/panozzaj/cursor-rules
Per session 177 This file is loaded in full into every session.
When invoked 177 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00177 $0.00177
Opus 5 $0.00088 $0.00088
Sonnet 5 $0.00035 $0.00035
Haiku 4.5 $0.00018 $0.00018

Measured yesterday against content hash 8b5456ef442a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

three-js 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.

rules/three-js.mdc · 31 lines

What it actually says

Three (library)

Ensure that all THREE.Vectors correctly have a closing parenthesis at the end. Otherwise we get a syntax error.

Example of failure case:

        startPoint = new THREE.Vector3(
          points[0].x,
          points[0].y,
          points[0].z + startPercent * stripeLength * Math.sign(points[1].z - points[0].z)
    }

Example of success case:

        endPoint = new THREE.Vector3(
          points[0].x,
          points[0].y,
          points[0].z + endPercent * stripeLength * Math.sign(points[1].z - points[0].z)
        )

Definitely do not fix with sed and/or create .bak files.

Changes

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.

  1. yesterday First seen · 31 lines · 177 tokens per session scan A 8b5456ef442a

Subscribe to this mod's changes

three-js is a cursor rule published in the GitHub repository panozzaj/cursor-rules (3 stars, last pushed 1y ago), licensed MIT. It adds 177 tokens to every session, about $0.0009 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.