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-python-scriptinggit 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-python-scripting)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/nuke-python-scripting"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-python-scripting/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-python-scripting"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-python-scripting.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.00060 | $0.02870 |
| Opus 5.5 | $0.00024 | $0.01148 |
| Sonnet 5.5 | $0.00012 | $0.00574 |
| Haiku 4.5 | $0.00006 | $0.00287 |
Grade A, and why
nuke-python-scripting 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
nuke-python-scripting
Version: 1.0.1 Last Updated: 2025-12-03 Dependencies: Nuke (Foundry), NukeMCPLogger
Overview
Python scripting patterns for Nuke compositing automation using the NukeMCPLogger pattern for structured output capture. All scripts follow Article I (general purpose - work on any project).
Critical Pattern: NukeMCPLogger provides dual-output logging (MCP response + persistent file) since Nuke MCP bridge doesn't capture print statements.
Quick Start
NukeMCPLogger Basic Usage
from nuke_mcp_logger import NukeMCPLogger
import nuke
# Create logger
log = NukeMCPLogger(session_name="MyTask")
try:
log.info("Starting operation...")
# Create node
grade_node = nuke.createNode("Grade")
log.increment_stat("nodes_created")
log.success(f"Created node: {grade_node.name()}")
except Exception as e:
log.error("Operation failed", e)
# Return to MCP
result = log.get_results()
Expected Output:
{
"status": "success",
"session": "MyTask",
"logs": ["Starting operation...", "Created node: Grade1"],
"errors": [],
"warnings": [],
"stats": {"nodes_created": 1},
"timestamp": "2025-12-03T..."
}
Standard Workflows
Workflow 1: General Purpose Node Creation
Use When: Creating any type of Nuke node in any project
def create_node_general(node_type: str, name: str = None):
"""
Create any Nuke node - works for ALL projects (Article I).
Args:
node_type: Nuke node class (Read, Grade, Merge2, etc.)
name: Optional custom name
Returns:
dict: Logger results with success/error status
"""
import nuke
from nuke_mcp_logger import NukeMCPLogger
log = NukeMCPLogger(session_name="CreateNode")
try:
node = nuke.createNode(node_type)
if name:
node.setName(name)
log.set_stat("node_type", node_type)
log.set_stat("node_name", node.name())
log.success(f"Created {node_type}: {node.name()}")
return log.get_results()
except Exception as e:
log.error(f"Failed to create {node_type}", e)
return log.get_results()
# Usage
result = create_node_general("Grade", "ShotGrade")
result = create_node_general("Merge2")
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 · 455 lines · 60 tokens per session scan A c48ac935f8c0
nuke-python-scripting is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 60 tokens to every session and 2,870 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
artclaw-tool-executor
An instruction set for running tools from the ArtClaw Tool Manager, an interface for choosing and executing registered tools.
ue5-cpp-gameplay
UE5.6/UE5.7 gameplay C++ implementation for Actors, Components, DataAssets, and gameplay logic. Use when requests ask to write .h/.cpp pairs, expose UPROPERTY/UFUNCTION to Blueprint, use GameplayTags, or build reusable component-based systems.
content-hash-cache-pattern
Cache expensive file processing results using SHA-256 content hashes — path-independent, auto-invalidating, with service layer separation.
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
comfyui-node-registry
Authoring & publishing ComfyUI custom nodes to the Comfy Registry, covering node structure, pyproject.toml spec, comfy-cli publishing, and CI.