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/12-studio/tackl/react-three-fibernpx skills add 12-Studio/Tackl --skill react-three-fibergit clone --depth 1 https://github.com/12-Studio/TacklWrote 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/12-studio/tackl/react-three-fiber)<a href="https://agentmods.dev/skills/12-studio/tackl/react-three-fiber"><img src="https://agentmods.dev/badge/skills/12-studio/tackl/react-three-fiber.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.00071 | $0.06337 |
| Opus 5 | $0.00036 | $0.03168 |
| Sonnet 5 | $0.00014 | $0.01267 |
| Haiku 4.5 | $0.00007 | $0.00634 |
Grade A, and why
react-three-fiber 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 4d 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.
This is a copy
100% identical to react-three-fiber — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 1,080 lines — stays where its author put it; the contents beside it link to each section on GitHub.
React Three Fiber
Overview
React Three Fiber (R3F) is a React renderer for Three.js that brings declarative, component-based 3D development to React applications. Instead of imperatively creating and managing Three.js objects, you build 3D scenes using JSX components that map directly to Three.js objects.
When to Use This Skill:
- Building 3D experiences within React applications
- Creating interactive product configurators or showcases
- Developing 3D portfolios, galleries, or storytelling experiences
- Building games or simulations in React
- Adding 3D elements to existing React projects
- When you need state management and React hooks with 3D graphics
- When working with React frameworks (Next.js, Gatsby, Remix)
Key Benefits:
- Declarative: Write 3D scenes like React components
- React Integration: Full access to hooks, context, state management
- Reusability: Create and share 3D component libraries
- Performance: Automatic render optimization and reconciliation
- Ecosystem: Works with Drei helpers, Zustand, Framer Motion, etc.
- TypeScript Support: Full type safety for Three.js objects
Core Concepts
1. Canvas Component
The <Canvas> component sets up a Three.js scene, camera, renderer, and render loop.
import { Canvas } from '@react-three/fiber'
function App() {
return (
<Canvas
camera={{ position: [0, 0, 5], fov: 75 }}
gl={{ antialias: true }}
dpr={[1, 2]}
>
{/* 3D content goes here */}
</Canvas>
)
}
Canvas Props:
camera- Camera configuration (position, fov, near, far)gl- WebGL renderer settingsdpr- Device pixel ratio (default: [1, 2])shadows- Enable shadow mapping (default: false)frameloop- "always" (default), "demand", or "never"flat- Disable color management for simpler colorslinear- Use linear color space instead of sRGB
2. Declarative 3D Objects
Three.js objects are created using JSX with kebab-case props:
What ships with it
13 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.
- assets/examples/README.md 16 KB
- assets/starter_r3f/index.html 1.6 KB
- assets/starter_r3f/package.json 570 B
- assets/starter_r3f/README.md 5.5 KB
- assets/starter_r3f/src/App.jsx 282 B
- assets/starter_r3f/src/components/Box.jsx 945 B
- assets/starter_r3f/src/components/Sphere.jsx 638 B
- assets/starter_r3f/src/Experience.jsx 1.3 KB
- assets/starter_r3f/src/main.jsx 208 B
- assets/starter_r3f/vite.config.js 406 B runs code
- references/api_reference.md 18 KB
- scripts/component_generator.py 19 KB runs code
- scripts/scene_setup.py 18 KB runs code
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.
- 4d ago First seen · 1,080 lines · 71 tokens per session scan A f9747e9e93bf
react-three-fiber is a skill published in the GitHub repository 12-Studio/Tackl (10 stars, last pushed 9d ago), licensed MIT. It adds 71 tokens to every session and 6,337 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to react-three-fiber, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
capacitor-ios
Build and ship Three.js apps on Capacitor iOS with Vite and Swift Package Manager: GLTF loading, assetsindex animation UI, OrbitControls mouse/touch mappings, and iOS sync/run troubleshooting.
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
react-doctor
Use when finishing a feature, fixing a bug, before committing React code, or when the user types /doctor, asks to scan, triage, or clean up React diagnostics. Covers lint, accessibility, bundle size, architecture. Includes a regression check and a full local-triage workflow that fetches the canonical playbook.
framer-motion
Creates smooth animations and micro-interactions using Framer Motion including page transitions, gestures, scroll-based animations, and orchestrated sequences. Use when users request "add animation", "framer motion", "page transition", "animate component", or "micro-interactions".
remotion-best-practices
Best practices for Remotion - Video creation in React.
remotion-best-practices
Best practices for Remotion.