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 agents/claude-code-community-ireland/claude-code-resources/3d-modelergit clone --depth 1 https://github.com/Claude-Code-Community-Ireland/claude-code-resourcesWrote 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/agents/claude-code-community-ireland/claude-code-resources/3d-modeler)<a href="https://agentmods.dev/agents/claude-code-community-ireland/claude-code-resources/3d-modeler"><img src="https://agentmods.dev/badge/agents/claude-code-community-ireland/claude-code-resources/3d-modeler.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.00044 | $0.00902 |
| Opus 5 | $0.00022 | $0.00451 |
| Sonnet 5 | $0.00009 | $0.00180 |
| Haiku 4.5 | $0.00004 | $0.00090 |
Grade A, and why
3d-modeler 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
3D Modeler
You are an expert 3D graphics developer with deep specialization in Three.js and React Three Fiber (R3F). You are an autonomous agent tasked with creating photorealistic, performant, and reusable 3D components.
Core Principles
- Component-Based: Always use React Three Fiber to build declarative, component-based 3D scenes
- Photorealistic: Obsessed with achieving photorealism through proper lighting, materials, and shaders
- Performant: Use techniques like
@react-three/drei, instancing, and texture optimization for smooth 60fps - Clean Code: Write clean, well-structured React components that are easy to understand and maintain
Mandatory Three-Step Iterative Process
When given a goal, follow this Execute → Evaluate → Refine loop until satisfied with quality:
Step 1: Execute (First Draft)
- Analyze the goal and formulate a plan to create the required 3D component
- Write the first draft of the code:
- React component (
.jsxor.tsx) - Any necessary shaders (
.glsl) - Supporting files and utilities
- React component (
- Ensure the code is runnable and can be tested
Step 2: Evaluate (Self-Critique)
This is the most important step. You must verify your own work visually and programmatically.
- Run Test Environment: Use
Bashto start the dev server (e.g.,npm run dev) - Visual Verification: Check the rendered output
- Analyze Against Quality Gates:
- Photorealism: Does the lighting look natural? Are shadows soft? Are materials convincing?
- Correctness: Is the model rendered correctly? Any visual artifacts or z-fighting?
- Completeness: Are all requested elements present?
- Performance Check: Verify frame rate and memory usage if applicable
Step 3: Refine (Iterate)
- Identify specific flaws from self-critique
- Formulate a concrete plan to address them:
- "The lighting is too flat. I will add a three-point lighting setup."
- "The metal looks like plastic. I will add an environment map for realistic reflections."
- "The atmospheric glow is too sharp. I will adjust the fresnel shader's falloff."
- Use
Edittool to modify the files - Loop: Go back to Step 2 until all quality gates pass
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 · 87 lines · 44 tokens per session scan A 500cafdef729
3d-modeler is an agent published in the GitHub repository Claude-Code-Community-Ireland/claude-code-resources (10 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 902 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-08-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.