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 dcc-mcp/dcc-mcp-blender --skill blender-geometry-nodesgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-blenderWrote 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/dcc-mcp/dcc-mcp-blender/blender-geometry-nodes)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-blender/blender-geometry-nodes"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-blender/blender-geometry-nodes/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/dcc-mcp/dcc-mcp-blender/blender-geometry-nodes"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-blender/blender-geometry-nodes.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.00026 | $0.00802 |
| Opus 5 | $0.00013 | $0.00401 |
| Sonnet 5 | $0.00005 | $0.00160 |
| Haiku 4.5 | $0.00003 | $0.00080 |
Grade A, and why
blender-geometry-nodes 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blender-geometry-nodes
Typed tools for creating Geometry Nodes groups, assigning them to mesh
modifiers, setting exposed modifier inputs, and inspecting procedural graph
state. Use blender-shader-nodes for low-level shared node graph operations
such as list_nodes, connect_nodes, and set_node_input.
Interface socket workflow (Blender 4.0+)
Use inspect_geometry_node_interface to read socket identifiers, directions,
basic defaults, the group-user count and an interface revision. The query
rejects interfaces over 256 items or text fields over 1024 UTF-8 bytes; it does
not return a partial revision.
Blender 3.6 reports interface_api_unavailable for these new tools.
Pass the exact revision to create_geometry_node_socket,
update_geometry_node_socket, or remove_geometry_node_socket. Updates and
removal require the returned identifier, not a potentially ambiguous label.
Read back after each edit and use the new revision. Stale revisions fail before
editing; never drop the guard or retry with guessed identifiers.
Creation supports Geometry, Float, Int, Bool, Vector, Color, and String socket
types in either direction. Updates preserve identity and can change the name,
description, or a supported basic default. Numeric defaults are finite within
+/-1000000; vectors have three components and colors have four. Names are
limited to 63 UTF-8 bytes; descriptions and string defaults to 1024 bytes.
Use set_geometry_node_modifier_input for an individual modifier's input
value; changing a group interface default is not a per-object override.
Interface edits affect all users of the group. Linked/library-override groups are refused by these mutating tools. Removing a socket can disconnect links and discard per-instance inputs. After a native edit starts, a failure reports possible mutation and no rollback; inspect before retrying.
The process-local revision covers the queried interface layout, labels, directions, types, descriptions and supported basic defaults, not evaluated geometry, links or per-modifier values. Panel CRUD, socket-type replacement, object/material/collection references, menus, field-domain controls and zones remain outside this first interface slice. The graph-info tool does not prove that evaluated geometry matches the intended result.
What ships with it
11 files 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.
- scripts/add_geometry_nodes_modifier.py 1.1 KB runs code
- scripts/assign_geometry_node_group.py 458 B runs code
- scripts/create_geometry_node_group.py 453 B runs code
- scripts/create_geometry_node_socket.py 374 B runs code
- scripts/evaluate_geometry_nodes_info.py 470 B runs code
- scripts/inspect_geometry_node_interface.py 374 B runs code
- scripts/list_geometry_nodes_modifiers.py 2.3 KB runs code
- scripts/remove_geometry_node_socket.py 374 B runs code
- scripts/set_geometry_node_modifier_input.py 478 B runs code
- scripts/update_geometry_node_socket.py 374 B runs code
- tools.yaml 9.4 KB
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 Changed · +36 lines · +7 tokens per session 7ae96b8cc263
- 11d ago First seen · 40 lines · 19 tokens per session scan A a40e3703d6ae
blender-geometry-nodes is a skill published in the GitHub repository dcc-mcp/dcc-mcp-blender (30 stars, last pushed today), licensed MIT. It adds 26 tokens to every session and 802 once invoked, about $0.0001 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-30.
Other skills, from other repositories
blender-reference-modeling
Build, compare, review, or repair a Blender model against an actual supplied image, photograph, concept, or visual reference using adaptive decomposition, measurable proportions, evidence scoring, and bounded repair. Use only when the request explicitly concerns model creation or quality against visual form criteria…
blender-bridge
Operate Blender Agent Bridge through its stable five-tool MCP gateway for scene inspection, modeling, materials, rigging, animation, simulation, rendering, external assets, trusted scripts, and preview decisions. Use whenever an agent must work in a live Blender scene through Blender Bridge, especially when only…
blender-mcp
Control Blender directly from Hermes via socket connection to the blender-mcp addon. Create 3D objects, materials, animations, and run arbitrary Blender Python (bpy) code. Use when user wants to create or modify anything in Blender.
dcc-mcp-core
Foundation library for the DCC Model Context Protocol (MCP) ecosystem. Provides Rust-powered action management, skills system, IPC transport, MCP Streamable HTTP server (2025-03-26 spec, with 2025-06-18 and 2025-11-25 awareness), sandbox security, shared memory, screen capture, USD scene support, and telemetry for…
maya-pipeline
Domain skill — Maya asset pipeline orchestration: set up project directory structures, export scenes to USD, and coordinate multi-step DCC workflows. Use when initialising a Maya project or exporting assets for a downstream pipeline. Not for raw geometry editing — use maya-geometry for that. Not for low-level USD file…
imagemagick-tools
Infrastructure skill — image processing and manipulation via ImageMagick: resize, composite, convert formats, add watermarks. Use when batch-processing textures, thumbnails, or rendered images at the file level. Not for in-DCC texture or material editing — use a domain skill bound to the specific DCC for that.