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 nuke-node-tree-patternsgit 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/nuke-node-tree-patterns)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/nuke-node-tree-patterns"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-node-tree-patterns/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/nuke-node-tree-patterns"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-node-tree-patterns.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.00038 | $0.03672 |
| Opus 5.5 | $0.00015 | $0.01469 |
| Sonnet 5.5 | $0.00008 | $0.00734 |
| Haiku 4.5 | $0.00004 | $0.00367 |
Grade A, and why
nuke-node-tree-patterns 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 — 497 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuke Node Tree Patterns
Version: 1.0.0 Last Updated: 2026-01-21 Status: Production-ready Dependencies: Nuke Python API
Production-tested patterns for creating robust, complex node trees programmatically in Nuke.
Purpose
This skill provides battle-tested patterns for Nuke Python automation, learned from building production tools like the auto-tiling system. These patterns solve common issues like unwanted auto-connections, positioning problems, and blending artifacts.
Core Patterns
1. Avoiding Auto-Connection Issues
Problem: nuke.createNode() auto-connects to selected nodes, causing unexpected connections.
Solution: Use nuke.nodes.X() and manage connections explicitly.
# [FAIL] BAD: Auto-connects unpredictably
transform = nuke.createNode('Transform', inpanel=False)
transform.setInput(0, input_node) # May already be connected!
# [OK] GOOD: Explicit control
for node in nuke.allNodes():
node.setSelected(False) # Deselect all first
transform = nuke.nodes.Transform() # Create without auto-connection
transform.setXYpos(x, y) # Position first
transform.setInput(0, input_node) # Then connect explicitly
Key Rules:
- Always deselect all nodes before creation:
for node in nuke.allNodes(): node.setSelected(False) - Use
nuke.nodes.X()instead ofnuke.createNode('X') - Position before connecting:
setXYpos()thensetInput() - Connect explicitly: Never rely on auto-connection
2. Dynamic Node Positioning
Problem: Hardcoded positions don't work when input nodes move.
Solution: Calculate positions relative to input node.
# [FAIL] BAD: Hardcoded positions
base_x = 0
base_y = 0
# [OK] GOOD: Dynamic from input
input_x = input_node.xpos()
input_y = input_node.ypos()
base_x = input_x + 200 # Offset to the right
base_y = input_y + 100 # Offset below
Typical Offsets:
- Horizontal spacing between tiles: 292px
- Vertical spacing (small): 43px
- Vertical spacing (before Expression): 97px
- Dot row below input: 200px
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 · 497 lines · 38 tokens per session scan A eac3013e60e3
nuke-node-tree-patterns is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 38 tokens to every session and 3,672 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…