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/random6913/claude-code-superkit/r3f-scroll-driven-3dnpx 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.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.00045 | $0.01180 |
| Opus 5 | $0.00023 | $0.00590 |
| Sonnet 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 today.
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.
- today 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 (2 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 1,180 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
apm-review-panel
Use this skill to run a multi-persona expert advisory review on a labelled pull request in microsoft/apm. The panel fans out to five mandatory specialists plus a test-coverage specialist (active on every PR that touches src/) plus three conditional specialists (auth, doc-writer, performance-expert), all running in…
apm-issue-autopilot
Use this skill to drive any open microsoft/apm issue (bug, feature, docs, refactor, perf) from raw intake to a mergeable PR with triage as the central, paramount gate. Run the apm-triage-panel rubric per issue first, then present ONE consolidated triage review for the whole batch and escalate to the maintainer BY…
cli-logging-ux
Use this skill when editing or creating CLI output, logging, warnings, error messages, progress indicators, or diagnostic summaries in the APM codebase. Activate whenever code touches console helpers (richsuccess, richwarning, richerror, richinfo, richecho), DiagnosticCollector, STATUSSYMBOLS, CommandLogger, or any…
cut-release
Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR…
docs-sync
Use this skill whenever a pull request is opened, reopened, or synchronized in microsoft/apm to assess whether and how the documentation corpus must change to stay truthful with the proposed code change. Activate even when the PR title or body says nothing about docs -- the skill must run on every PR to detect silent…
shepherd-driver
Use only as the composed drive-to-merge stage of an APM batch orchestrator (batch-bug-shepherd, apm-issue-autopilot) that has already selected ONE open pull request in microsoft/apm. Do NOT use for user-facing requests to triage issues, sweep a queue, or open PRs -- the parent orchestrator owns those. Spawn one…