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-node-graphgit 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-node-graph)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-houdini/houdini-node-graph"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-node-graph/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-node-graph"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-node-graph.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.00085 | $0.00657 |
| Opus 5 | $0.00043 | $0.00329 |
| Sonnet 5 | $0.00017 | $0.00131 |
| Haiku 4.5 | $0.00009 | $0.00066 |
Grade A, and why
houdini-node-graph 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 9d 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-node-graph
Typed node-graph relationship tools for agents. All tools are affinity: main
because they call hou. Prefer these over
houdini-scripting.execute_python for inspecting and wiring connections.
Tool groups
graph-inspect(read-only):inspect_network— full semantic analysis of a parent network: broken inputs, orphaned nodes, cycles, disconnected subgraphs, type-mismatched connections, chain roots and ends.graph-query(read-only):get_connections— inputs, outputs, dependents.graph-edit(mutating):connect_input,disconnect_input— explicit input/output indexes with structured failures.graph-layout(mutating):auto_layout— controllable auto-layout with user-position preservation. Two strategies:houdini_defaultandtree_left_to_right. Supportsdry_runfor preview andpreserve_user_layoutto skip user-touched nodes.
Suggested flows
Semantic inspection
inspect_network("/obj/geo1")— get the full health picture- Diagnose: broken inputs → missing connections, orphaned nodes → unused generators, cycles → feedback loops, subgraphs > 1 → fragmented network
- Fix with
connect_input/disconnect_input
Auto-layout with user preservation
auto_layout(parent_path="/obj/geo1", dry_run=true)— preview what will move- Confirm the plan:
preserved_pathscontains user-touched nodes left untouched auto_layout(parent_path="/obj/geo1")— apply layout, preserving user positions- Optionally switch strategy:
auto_layout(parent_path="/obj/geo1", strategy="tree_left_to_right")
For parameter edits use houdini-parameters; for node creation use
houdini-nodes.
What ships with it
7 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.
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.
- 9d ago First seen · 59 lines · 85 tokens per session scan A c8959b20489e
houdini-node-graph is a skill published in the GitHub repository dcc-mcp/dcc-mcp-houdini (12 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 657 once invoked, about $0.0004 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-import-to-scene
Pipeline stage — structured asset import. Consume an AssetDescriptor produced by maya-asset-source and import the asset (FBX, OBJ, USD) into the current Maya scene via cmds.file(). Handles axis/unit conversion, MaterialMode, PlacementHint, and optional target collection grouping. Returns an ImportToSceneResult with…
usd-tools
Infrastructure skill — low-level OpenUSD scene inspection and validation: read layer stacks, traverse prims, validate USD schemas. Use when working directly with raw USD files (usda, usdc, usdz) or verifying USD compliance. Not for Maya-specific USD export — use maya-pipelineexportusd for that. Not for full DCC…
maya-mesh-ops
Authoring stage — typed polygon construction and editing: loft, lathe, instance arrays, pivots, mirror, combine, separate, and cleanup. Use for creating or modifying polygon topology from explicit scene inputs. Not for primitive creation (use maya-primitives), construction-history or DG inspection (use…
maya-rigging
Authoring stage — character / prop rigging: joints, IK, skin clusters, deformers, blend shapes, control curves, skin weights, constraints, and optional rig framework detection. Use when constructing rigs. Not for keyframe animation (maya-animation), pose libraries (maya-pose-library), or final scene assembly…
maya-dynamics
Authoring stage - classic Maya dynamics primitives: rigid bodies, force fields, and field connections. Use for small simulation setup steps before baking with maya-animation. Not for keyframe editing (maya-animation), mesh modeling (maya-mesh-ops), or viewport output (maya-render).
maya-pose-library
Authoring stage — save / load / mirror character poses as JSON presets. Use for reusable pose libraries on rigged characters. Not for keyframe animation (maya-animation) or rigging setup (maya-rigging).