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 Bbeierle12/Skill-MCP-Claude --skill r3f-routergit clone --depth 1 https://github.com/Bbeierle12/Skill-MCP-ClaudeWrote 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/bbeierle12/skill-mcp-claude/r3f-router)<a href="https://agentmods.dev/skills/bbeierle12/skill-mcp-claude/r3f-router"><img src="https://agentmods.dev/badge/skills/bbeierle12/skill-mcp-claude/r3f-router/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/bbeierle12/skill-mcp-claude/r3f-router"><img src="https://agentmods.dev/badge/skills/bbeierle12/skill-mcp-claude/r3f-router.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.01543 |
| Opus 5 | $0.00029 | $0.00772 |
| Sonnet 5 | $0.00012 | $0.00309 |
| Haiku 4.5 | $0.00006 | $0.00154 |
Grade A, and why
r3f-router 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 11d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
R3F Router
Routes to 5 specialized React Three Fiber skills based on task requirements.
Routing Protocol
- Classify — Identify primary task type from user request
- Match — Find skill(s) with highest signal match
- Combine — Most R3F tasks need 2-4 skills together
- Load — Read matched SKILL.md files before implementation
Quick Route
Tier 1: Core (Always Consider)
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| Scene setup | r3f-fundamentals |
canvas, scene, camera, lights, render, useFrame |
| Custom shapes | r3f-geometry |
geometry, vertices, bufferAttribute, instancing, mesh |
| Surface appearance | r3f-materials |
material, shader, texture, uniform, color, PBR |
Tier 2: Enhanced (Add When Needed)
| Task Type | Skill | Primary Signal Words |
|---|---|---|
| Optimization | r3f-performance |
performance, FPS, draw calls, LOD, culling, memory |
| Helpers/Controls | r3f-drei |
OrbitControls, useGLTF, Text, Environment, Html |
Signal Matching Rules
Priority Order
When multiple signals present, resolve by priority:
- Explicit component — "add OrbitControls" →
r3f-drei - Specific technique — "use instancing" →
r3f-geometry - Problem domain — "custom shader" →
r3f-materials - Default tier — Fall back to
r3f-fundamentals
Confidence Scoring
- High (3+ signals) — Route immediately
- Medium (1-2 signals) — Route with
r3f-fundamentalsas base - Low (0 signals) — Ask user for clarification
Common Combinations
Basic 3D Scene (3 skills)
r3f-fundamentals → Canvas, camera, lights, render loop
r3f-drei → OrbitControls, Environment, helpers
r3f-materials → MeshStandardMaterial, textures
Wiring: Fundamentals provides scene structure, drei adds controls and environment, materials define appearance.
Custom Shader Effect (3 skills)
r3f-fundamentals → Scene setup, useFrame for animation
r3f-geometry → Custom BufferGeometry if needed
r3f-materials → ShaderMaterial, uniforms, GLSL
What ships with it
1 file 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.
- 11d ago First seen · 181 lines · 58 tokens per session scan A ef524bc27c98
r3f-router is a skill published in the GitHub repository Bbeierle12/Skill-MCP-Claude (8 stars, last pushed yesterday), licensed MIT. It adds 58 tokens to every session and 1,543 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-31.
Other skills, from other repositories
fast-dash
Build a Fast Dash web app from a Python function. Use when the user wants to turn a function into an interactive app, add a UI to an existing function, or build a dashboard / form / wizard. Fast Dash infers UI components from type hints, so a well-typed function becomes an app with one decorator.
developing-with-streamlit
Use for ALL Streamlit tasks: creating, editing, debugging, beautifying, styling, theming, optimizing, or deploying Streamlit apps. Also custom components, st.components.v2, HTML/JS/CSS work. Discovers and loads version-matched reference docs from the user's installed Streamlit (>=1.57). Triggers: streamlit, st.…
huggingface-gradio
Build Gradio web UIs and demos in Python. Use when creating or editing Gradio apps, components, event listeners, layouts, or chatbots.
wiring-vizro-actions
Use this skill when adding cross-filter, cross-highlight, drill-through, or data export interactions to a Vizro dashboard — both for choosing the right interaction pattern during design and for implementing actions in code. Activate when the user wants clicks on a chart or table to filter or highlight other charts…
stripe-apps
Use when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g. "add a panel to the customer page", "customize my Stripe Dashboard", "react to Stripe events from my app", "connect my service to Stripe without sharing API keys"). Covers the full app development…
frontend-feature
Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.