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-texture-bakegit 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-texture-bake)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-houdini/houdini-texture-bake"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-texture-bake/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-texture-bake"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-houdini/houdini-texture-bake.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.00073 | $0.01185 |
| Opus 5 | $0.00036 | $0.00593 |
| Sonnet 5 | $0.00015 | $0.00237 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
houdini-texture-bake 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
houdini-texture-bake
Typed texture-baking tools that bake geometry attributes to image files using Houdini's Bake Texture ROP, Labs Maps Baker, or COP-based fallback workflows.
Bake method detection
Tools auto-detect the best available bake method at runtime:
- Labs Maps Baker (
sidefx_labs→maps_baker) — richest option, single-node multi-map bake with 20+ map types (normals, cavity, curvature, thickness, roughness, metallic, etc.) - Bake Texture ROP (
game_simple_baker/baker::2.0) — built-in Houdini 20+ ROP for standard map baking - COP fallback — simple per-attribute COP-based bake when neither Labs nor Bake Texture ROP is available
When no bake method is detected, tools return a structured diagnostic payload
(available_methods: [], recommendations: [...]) — they never degrade to raw
execute_python.
Tool groups
bake-ao:bake_ambient_occlusion— bake ambient occlusion to texture (async, 900s timeout)bake-lighting:bake_lighting— bake scene lighting via Mantra/Karma render-to-texture (async, 900s timeout)bake-textures:bake_textures— general multi-map baking (diffuse, normals, cavity, curvature, roughness, metallic, etc.) via Labs Maps Baker or Bake Texture ROP (async, 1800s timeout)bake-query:list_bake_targets— scan geometry for UV-equipped, bake-compatible nodes (sync, read-only)bake-transfer:transfer_maps— transfer normals/displacement/diffuse from high-res source to low-res target (async, 1200s timeout)
Context limitations
- UV requirement: Bake Texture ROP and Labs Maps Baker both require the
target geometry to have non-degenerate UVs.
list_bake_targetsreportshas_uvsso callers can verify before baking. - Renderer selection:
bake_lightingsupportsmantra(default) andkarma. Karma requires a valid XPU/CPU license. - Labs Maps Baker: Install via
sidefx_labspackage or Houdini Game Dev Toolset. Detection is automatic; tools reportlabs_maps_baker_availablein their result payload.
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.
- 11d ago First seen · 99 lines · 73 tokens per session scan A 0a80636d6af6
houdini-texture-bake is a skill published in the GitHub repository dcc-mcp/dcc-mcp-houdini (12 stars, last pushed today), licensed MIT. It adds 73 tokens to every session and 1,185 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-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…