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 sideshowroberto/vfx-agent-toolkit --skill houdini-hda-creationgit clone --depth 1 https://github.com/sideshowroberto/vfx-agent-toolkitWrote 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/sideshowroberto/vfx-agent-toolkit/houdini-hda-creation)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/houdini-hda-creation"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/houdini-hda-creation/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/sideshowroberto/vfx-agent-toolkit/houdini-hda-creation"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/houdini-hda-creation.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.00054 | $0.04796 |
| Opus 5.5 | $0.00022 | $0.01918 |
| Sonnet 5.5 | $0.00011 | $0.00959 |
| Haiku 4.5 | $0.00005 | $0.00480 |
Grade A, and why
houdini-hda-creation 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 — 690 lines — stays where its author put it; the contents beside it link to each section on GitHub.
houdini-hda-creation
Version: 1.1.1 Last Updated: 2026-10-09 Dependencies: Houdini 20+, Python 3.9+
CRITICAL: MANDATORY FIRST STEP
ALWAYS verify Houdini environment before execution:
# Check Houdini installation
where houdini
# Verify Houdini version
houdini --version
# Check if Houdini is running (Windows)
tasklist | findstr "houdini"
Why Critical:
- Asset Corruption: Creating HDAs while Houdini is saving can corrupt asset definitions
- Version Compatibility: HDAs created in newer Houdini versions may not work in older versions
- Path Requirements: HDA libraries must be accessible via HOUDINI_PATH or $HIP
QUICK START
Most Common Use Case: Create Basic HDA
Goal: Convert a subnet into a reusable Houdini Digital Asset
Step 1: Validate Environment
import hou
# Check Houdini session is active
if not hou.hipFile.isLoadingHipFile():
print("Ready to create HDA")
else:
print("Wait for file to finish loading")
Step 2: Prepare Node Network
# Select the subnet you want to convert
subnet = hou.node("/obj/my_subnet")
# Verify subnet exists and is valid
if subnet and subnet.type().name() == "subnet":
print(f"Valid subnet: {subnet.path()}")
else:
raise ValueError("Invalid subnet selected")
Step 3: Create HDA from Subnet
# Define HDA properties
hda_name = "my_tool"
hda_label = "My Tool"
hda_file = f"$HIP/hda/{hda_name}.hda"
# Create the digital asset
subnet.createDigitalAsset(
name=hda_name,
hda_file_name=hda_file,
description=hda_label,
min_num_inputs=0,
max_num_inputs=1
)
print(f"HDA created: {hda_file}")
Step 4: Verify Success
# Check HDA definition was created
node_type = hou.nodeType(hou.objNodeTypeCategory(), hda_name)
if node_type:
print(f"HDA type registered: {node_type.name()}")
print(f"Definition file: {node_type.definition().libraryFilePath()}")
else:
print("ERROR: HDA not registered")
What ships with it
1 file 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.
- today First seen · 690 lines · 54 tokens per session scan A 9fad2b962fc9
houdini-hda-creation is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 54 tokens to every session and 4,796 once invoked, about $0.0002 per session on Opus 5.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-11-02.
Other skills, from other repositories
dcc-cua
A routing guide for controlling application interfaces through the project’s DCC-CUA system. DCC applications are digital-content tools such as Maya, Blender, and Houdini.
mesh-ops
Cross-adapter polygon modeling recipe pack for the shared cross-DCC modeling vocabulary. Structured RECIPES.yaml entries for primitive creation, hard-surface edits, topology cleanup, UV generation, radial arraying, and material assignment. Reusable by every DCC adapter's mesh-ops skill (maya, blender, houdini, 3dsmax…
marketplace-publish-extension
Infrastructure skill — publish (register/update) an extension package to a marketplace catalog. Reads the extension's SKILL.md frontmatter, constructs a CatalogEntry, and upserts it into the target marketplace.json. Optionally commits and pushes when the catalog source is a git repository. Use after scaffolding an…
marketplace-create-extension
Infrastructure skill — scaffold a new marketplace extension package (SKILL.md + tools.yaml + scripts/) with MIT-0 licensing. Use when creating a publishable marketplace entry for any DCC host. Not for editing existing extensions or driving live DCC scenes — use domain skills for that.
clawhub-compat
Example skill — demonstrates full compatibility with the ClawHub/OpenClaw skill format. Use as a reference when creating skills for both the dcc-mcp-core ecosystem and ClawHub marketplace. Not intended for production use — this is an authoring reference only.
example-layered-skill
Example skill — reference implementation of the internal layered architecture pattern (Tools / Services / Utils) for complex skills with shared business logic. Use as a template when a skill outgrows a single scripts/execute.py file. Not intended for production use — see docs/guide/skills.md for the architectural…