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 HitamLegit6777/blender-mcp-ultra --skill text-to-blendergit clone --depth 1 https://github.com/HitamLegit6777/blender-mcp-ultraWrote 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/hitamlegit6777/blender-mcp-ultra/text-to-blender)<a href="https://agentmods.dev/skills/hitamlegit6777/blender-mcp-ultra/text-to-blender"><img src="https://agentmods.dev/badge/skills/hitamlegit6777/blender-mcp-ultra/text-to-blender/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/hitamlegit6777/blender-mcp-ultra/text-to-blender"><img src="https://agentmods.dev/badge/skills/hitamlegit6777/blender-mcp-ultra/text-to-blender.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.00000 | $0.00374 |
| Opus 5.5 | $0.00000 | $0.00150 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
text-to-blender 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 2mo 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.
What it actually says
text-to-blender — Orchestrator Skill
Entry point for natural language → Blender scene generation. Chain-loads sub-skills based on user intent.
Intent Detection
Parse user request and decide which sub-skills to load:
User: "create a red chair with three-point lighting and render"
→ modeling + materials + lighting + cameras + rendering
User: "animate the sphere moving from left to right"
→ animation
User: "export the scene as glTF"
→ export
User: "make a 3D model from this wireframe sketch"
→ wireframe-to-3d
Workflow Sequence (Pro Mode)
- Block-out: Create primitive shapes with correct proportions
- Camera: Set up framing and composition
- Lighting: Add environment or artificial lights
- Forms: Refine geometry with modifiers
- Materials: Apply colors and PBR materials
- Detail: Add edge loops, bevels, subdivisions
- Render: Configure engine, resolution, output
- Composite: Post-processing (optional)
- Export: GLTF/FBX/USD/STL
Conventions
- Use execute_blender_code() for all geometry operations
- Name objects with prefixes: GEO_ (geometry), MAT_ (material), LGT_ (light), CAM_ (camera)
- Always apply transforms before exporting
- Validate with get_viewport_screenshot_image() after each phase
Example Chain
text-to-blender
→ blender-pro-workflow (sequencing)
→ blender-modeling
→ blender-materials
→ blender-lighting
→ blender-cameras
→ blender-rendering
→ blender-export
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.
- 2mo ago First seen · 55 lines · 0 tokens per session scan A b3b7fd30f4ae
text-to-blender is a skill published in the GitHub repository HitamLegit6777/blender-mcp-ultra (1 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 374 tokens. 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.
text-to-blender compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| text-to-blenderHitamLegit6777/blender-mcp-ultra | Skill | 1 | 2mo ago | MIT | A | 0 | Claude Code, Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |