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-rendergit 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-render)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-houdini/houdini-render"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-render/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-render"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-render.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.00061 | $0.01801 |
| Opus 5 | $0.00030 | $0.00901 |
| Sonnet 5 | $0.00012 | $0.00360 |
| Haiku 4.5 | $0.00006 | $0.00180 |
Grade A, and why
houdini-render 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 10d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
houdini-render
Typed render and visual-verification tools. Scene inspection and launch tools
use affinity: main; background job polling and cancellation use affinity: any.
Viewport tools are UI-aware: in a headless hython session they return a
structured warnings payload with captured: false instead of failing, so an
agent can detect and skip cleanly when rendering is unavailable.
OpenGL ROP rendering is likewise rejected in headless Houdini because the
native viewport/Vulkan path may terminate the process; use interactive Houdini
or Karma/Husk for batch rendering.
Tool groups
viewport:capture_viewport(single frame),flipbook(range with an optional positive increment and explicit camera). Both clamp resolution to 4096 and returnwritten_files/skipped/warnings.render:get_render_settings(read-only),set_render_settings(reportsunsupportedfields per ROP type),render_rop(foreground or isolatedhythonbackground job),get_render_job(polls and reconciles status without blocking the UI),finalize_render_outputs(publishes externally validated staged EXRs without replacing finals),cancel_render_job(cancels only jobs owned by the current adapter process),configure_aovs(add/remove Solaris RenderVars or native Mantra auxiliary planes with renderer-correct processing),validate_karma_stage(read-only USD/Karma preflight),get_render_stats(read resolution/samples/renderer/output).render_layer:create_render_layer(Solaris RenderProduct or cloned Mantra ifd ROP with its own output and object masks),manage_takes(take lifecycle plus parameter-tuple overrides for render variants).
Tracer-bullet flow
Viewport/Render
houdini_camera_light__create_camera(name="rendercam")set_render_settings(rop_path="/out/mantra1", camera="/obj/rendercam", resolution=[1280,720], output_path="/tmp/beauty.exr")get_render_settings("/out/mantra1")→ verifycapture_viewport(output_path="/tmp/preview.jpg")for a quick look (UI only; decoded dimensions and pixel extrema are verified, and degenerate frames fail closed)flipbook(output_path="/tmp/preview.$F4.jpg", frame_range=[1,24,4], camera_path="/obj/rendercam")for a sparse camera preview (UI only)render_rop("/out/mantra1", frame_range=[1,1])→ backgroundjob_idin interactive or headless Houdini
What ships with it
21 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/_background_render.py 877 B runs code
- scripts/_flipbook_chunked.py 17 KB runs code
- scripts/_render_common.py 7.8 KB runs code
- scripts/_render_worker.py 13 KB runs code
- scripts/_rop_chunked.py 13 KB runs code
- scripts/cancel_flipbook_job.py 251 B runs code
- scripts/cancel_render_job.py 648 B runs code
- scripts/capture_viewport.py 9.4 KB runs code
- scripts/configure_aovs.py 9.7 KB runs code
- scripts/create_render_layer.py 6.3 KB runs code
- scripts/finalize_render_outputs.py 829 B runs code
- scripts/flipbook.py 6.4 KB runs code
- scripts/get_flipbook_job.py 243 B runs code
- scripts/get_render_job.py 673 B runs code
- scripts/get_render_settings.py 8.6 KB runs code
- scripts/get_render_stats.py 2.9 KB runs code
- scripts/manage_takes.py 6.8 KB runs code
- scripts/render_rop.py 8.4 KB runs code
- scripts/set_render_settings.py 2.8 KB runs code
- scripts/validate_karma_stage.py 6.6 KB runs code
- tools.yaml 19 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.
- 10d ago First seen · 121 lines · 61 tokens per session scan A 444c6821abac
houdini-render is a skill published in the GitHub repository dcc-mcp/dcc-mcp-houdini (12 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,801 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
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-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-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…