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 RaNDoM6913/claude-code-superkit --skill r3f-scroll-driven-3dgit clone --depth 1 https://github.com/RaNDoM6913/claude-code-superkitWrote 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/random6913/claude-code-superkit/r3f-scroll-driven-3d)<a href="https://agentmods.dev/skills/random6913/claude-code-superkit/r3f-scroll-driven-3d"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/r3f-scroll-driven-3d/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/random6913/claude-code-superkit/r3f-scroll-driven-3d"><img src="https://agentmods.dev/badge/skills/random6913/claude-code-superkit/r3f-scroll-driven-3d.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.00045 | $0.01180 |
| Opus 5.5 | $0.00018 | $0.00472 |
| Sonnet 5.5 | $0.00009 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
r3f-scroll-driven-3d 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 1mo 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scroll-Driven 3D with GSAP + R3F
Architecture pattern for connecting GSAP ScrollTrigger to React Three Fiber scenes via Zustand store.
Why This Pattern?
Problem: GSAP runs in the DOM. R3F runs in WebGL. They can't communicate directly.
Solution: Zustand store as a bridge — GSAP writes scroll progress, R3F reads it in useFrame.
[GSAP ScrollTrigger] → writes → [Zustand Store] → reads → [R3F useFrame]
(DOM) (shared state) (WebGL)
Why Zustand (Not React State/Context)?
- React state/context triggers re-renders on every scroll tick (60fps = 60 re-renders/sec)
- Zustand
getState()reads directly without subscribing — zero re-renders - useFrame already runs at 60fps — just read the latest value
Implementation
Step 1: Create the store
// stores/useScrollStore.ts
import { create } from 'zustand';
interface ScrollStore {
progress: number; // 0-1 scroll progress
currentTexture: string; // active screen texture path
setProgress: (p: number) => void;
setTexture: (t: string) => void;
}
export const useScrollStore = create<ScrollStore>((set) => ({
progress: 0,
currentTexture: '/textures/screen-1.png',
setProgress: (p) => set({ progress: p }),
setTexture: (t) => set({ currentTexture: t }),
}));
Step 2: GSAP writes to store
// components/ScrollSection.tsx
import { useRef, useEffect } from 'react';
import gsap from 'gsap';
import { ScrollTrigger } from 'gsap/ScrollTrigger';
import { useScrollStore } from '@/stores/useScrollStore';
gsap.registerPlugin(ScrollTrigger);
export function ScrollSection() {
const ref = useRef<HTMLDivElement>(null);
const { setProgress, setTexture } = useScrollStore();
useEffect(() => {
const ctx = gsap.context(() => {
const tl = gsap.timeline({
scrollTrigger: {
trigger: ref.current,
start: 'top top',
end: 'bottom bottom',
scrub: 1, // number, NOT true
invalidateOnRefresh: true, // MUST have
pin: true,
},
});
// Animate progress 0 → 1
tl.to({}, {
duration: 1,
onUpdate: function() {
setProgress(this.progress());
},
});
// Swap texture at 50% scroll
tl.call(() => setTexture('/textures/screen-2.png'), [], 0.5);
// CRITICAL: extend timeline to full duration
tl.set({}, {}, 1.0);
}, ref);
return () => ctx.revert();
}, []);
return <div ref={ref} style={{ height: '300vh' }} />;
}
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.
- 1mo ago First seen · 163 lines · 45 tokens per session scan A e07ff9ec6f01
r3f-scroll-driven-3d is a skill published in the GitHub repository RaNDoM6913/claude-code-superkit (3 stars, last pushed 4d ago), licensed MIT. It adds 45 tokens to every session and 1,180 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
nav-loop
Run tasks until complete with structured completion signals. Auto-invoke when user says "run until done", "keep going until complete", "iterate until finished", "loop mode", "autonomous mode".
visual-regression
Setup visual regression testing with Storybook stories, configuration, and CI/CD workflows. Supports Chromatic, Percy, BackstopJS. Auto-invoke when user says "set up visual regression", "add Chromatic tests", "add screenshot testing", or "set up Percy".
optimized-nextjs-typescript
Optimized Next.js TypeScript best practices with modern UI/UX, focusing on performance, security, and clean architecture.
algolia-search
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning.
impeccable
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for…
system-check
Read-only installation smoke test for skills, daemons, operational memory, cognitive runtime, nightly freshness, terminal evidence, and unique route ownership.