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-houdini --skill houdini-nodesgit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-houdiniWrote 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-houdini/houdini-nodes)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-houdini/houdini-nodes"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-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-houdini/houdini-nodes"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-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.00051 | $0.00673 |
| Opus 5 | $0.00026 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
houdini-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 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.
What it actually says
houdini-nodes
Typed HOM node-graph operations for agents. Prefer these tools before using
houdini-scripting.execute_python.
Common Flow
create_nodeset_node_parmsconnect_nodes- Choose the cook contract:
cook_nodefor one expected-short live-scene cook. It is an async core job but nativehou.Node.cook()remains monolithic.cook_nodes_chunkedfor several independently bounded nodes, one per Houdini event-loop tick.start_cook_jobfor one potentially long cook in isolatedhython. Save the HIP first, then pollget_cook_job; status remains readable after transport loss or adapter restart. A non-terminal result withworker_liveness: unknownis last-known state, not proof that the worker is still alive; keep polling the samejob_idand never launch a duplicate.
layout_children
Never retry a timed-out cook blindly. Keep the returned core or isolated
job_id, rediscover the Houdini instance, and query status first. If Houdini
crashed, wait for a new instance registration; persisted core jobs recover as
interrupted, while isolated cook status remains available on disk.
What ships with it
12 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/_node_common.py 1.7 KB runs code
- scripts/cancel_cook_job.py 480 B runs code
- scripts/connect_nodes.py 1.2 KB runs code
- scripts/cook_node.py 1.5 KB runs code
- scripts/cook_nodes_chunked.py 880 B runs code
- scripts/create_node.py 1.4 KB runs code
- scripts/delete_node.py 817 B runs code
- scripts/get_cook_job.py 477 B runs code
- scripts/layout_children.py 1.3 KB runs code
- scripts/set_node_parms.py 1.3 KB runs code
- scripts/start_cook_job.py 804 B runs code
- tools.yaml 10 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.
- 11d ago First seen · 69 lines · 51 tokens per session scan A e868aaa92b9e
houdini-nodes is a skill published in the GitHub repository dcc-mcp/dcc-mcp-houdini (12 stars, last pushed today), licensed MIT. It adds 51 tokens to every session and 673 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-30.
Other skills, from other repositories
maya-render
Pipeline stage — render globals, final-frame rendering, and viewport capture: configure render settings, query them, render frames, capture playblasts. Use for producing final or preview imagery. Not for modeling (maya-mesh-ops), animation editing (maya-animation), generic file import/export (maya-geometry), or render…
maya-scripting
Bootstrap stage — escape hatch for Maya work that has no packaged skill yet. Agents should prefer searchskills / dcccapabilitymanifest → loadskill → typed tools (inputSchema + annotations) from domain skills; use executepython or executemel only when no skill matches, for bulk in-process loops, or for API…
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…
dcc-mcp-maya-setup
Set up dcc-mcp-maya for an agent or operator: install Maya Python dependencies with mayapy, generate MCP host configuration, guide the user through loading the Maya plugin, and run a first live-tool smoke prompt.
maya-asset-source
Pipeline stage — asset discovery and resolution. Search local asset libraries, resolve paths to structured AssetDescriptor records, and surface candidate assets for downstream import. Use before maya-import-to-scene to locate what to import.
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…