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 scottstts/Threejs-Awesome-Graphics-Agent-Skills --skill threejs-camera-directiongit clone --depth 1 https://github.com/scottstts/Threejs-Awesome-Graphics-Agent-SkillsWrote 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/scottstts/threejs-awesome-graphics-agent-skills/threejs-camera-direction)<a href="https://agentmods.dev/skills/scottstts/threejs-awesome-graphics-agent-skills/threejs-camera-direction"><img src="https://agentmods.dev/badge/skills/scottstts/threejs-awesome-graphics-agent-skills/threejs-camera-direction/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/scottstts/threejs-awesome-graphics-agent-skills/threejs-camera-direction"><img src="https://agentmods.dev/badge/skills/scottstts/threejs-awesome-graphics-agent-skills/threejs-camera-direction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00496 |
| Opus 5 | $0.00029 | $0.00248 |
| Sonnet 5 | $0.00012 | $0.00099 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
threejs-camera-direction 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 9d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Camera Direction
Treat the camera as an authored visual system, not a passive viewport. Compose the subject, establish scale, choose a stable up frame, and make every mode handoff explicit.
Build order
- Define the design frame: subject size, screen occupancy, lens, near/far, motion, and horizon/up convention.
- Build camera targets in semantic frames: ship, body surface, docking axis, or scene-authored shot.
- Derive position and orientation independently, then combine them once.
- Add input orbit/look only inside declared yaw/pitch and spatial constraints.
- Add frame-rate-independent follow or a bounded spring where the reference uses inertia.
- Snapshot and restore camera projection/state when a scene owns it.
- Test mode transitions, cuts, pointer-lock reacquisition, resize, and large coordinates.
Read references/camera-rig-and-cinematic-systems.md for exact chase/side/orbit rigs, projection values, transition rules, floating-origin shot, pointer controls, and implementation limits.
Non-negotiable rules
- Use subject dimensions to derive offsets; do not tune one fixed distance for differently scaled assets.
- For planetary motion, derive up from the dominant body rather than global Y.
- Interpolate position with
lerpand orientation withslerp. - During an explicit handoff, use one interpolation stage. Do not stack a transition blend and a second follow smoother over the same interval.
- Re-sync yaw/pitch from the camera when pointer lock is acquired.
- Update the projection matrix whenever FOV, near, far, or aspect changes.
- Keep stars or infinite backgrounds camera-relative when large translation would create false parallax or precision loss.
- Restore camera and input ownership on scene disposal.
Routing boundary
Use $threejs-procedural-animation for object motion timelines, springs,
docking, staging, and debris. This skill owns how the scene is viewed and how
camera modes hand off.
What ships with it
2 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.
- 9d ago First seen · 49 lines · 58 tokens per session scan A 9559e63ade85
threejs-camera-direction is a skill published in the GitHub repository scottstts/Threejs-Awesome-Graphics-Agent-Skills (793 stars, last pushed 12d ago), licensed MIT. It adds 58 tokens to every session and 496 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-30.
Other skills, from other repositories
gameobject-component-destroy
Destroy one or more Components from a target GameObject. Missing (null) components are skipped — they cannot be destroyed. Use 'gameobject-find' and 'gameobject-component-get' to identify the components first.
unity-version-split
Split a C# file into Unity 6.5+ and pre-Unity 6.5 variants. Use when a file needs different implementations for different Unity versions due to API changes (e.g., EntityId vs int, GetEntityId vs GetInstanceID).
unity-addressables
Manage Addressables groups, entries, profiles and content builds (com.unity.addressables, reflection-based).
motion
How an agent turns a character mesh into a usable animated FBX — and how to judge whether the result is shippable.
playtest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
unity-manual-component
Manually add, configure, reorder, and copy components on GameObjects using Unity Editor UI. For one-off Inspector workflows that do not need REST automation.