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-shot-setupgit 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-shot-setup)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/nuke-shot-setup"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-shot-setup/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-shot-setup"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/nuke-shot-setup.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.00067 | $0.02904 |
| Opus 5.5 | $0.00027 | $0.01162 |
| Sonnet 5.5 | $0.00013 | $0.00581 |
| Haiku 4.5 | $0.00007 | $0.00290 |
Grade A, and why
nuke-shot-setup 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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuke Shot Setup
Version: 1.1.2
Batch setup of Nuke comp/visdev files, folder structures, and shot tracking CSV.
Script Location
scripts/batch_shot_setup.py (paths in this skill are relative to the skill directory)
Show Configs
configs/<show_name>.json -- per-show overrides for OCIO, LUTs, viewer, format, etc.
Only values that differ from the script's built-in defaults need to be in the JSON.
--show-config may be repeated and is applied in order, so the standard call is
--show-config configs/studio_defaults.json --show-config configs/<show>.json
(team defaults first, show overrides second; later files win). Start a show
file from configs/show_template.json.
Built-in defaults: Nuke 17.0 v2, ACEScg in/out, DWAA compression, 4608x3164, 23.976fps, and no OCIO config. The script prints the effective Nuke version and OCIO path at the top of every run and warns when OCIO is unset - point it at your team's config via studio_defaults.json (ocio_config key). A path baked into the script is always somebody's personal path on somebody else's machine.
An empty ocio_config is not neutral by itself. The warning only covers
the ocio_config key - the other colour keys (ACES - ACEScg read/write
colorspace, the Output - K1S1-like - Rec.709 viewer process, monitor LUTs)
still default to ACES-specific names even when no OCIO config is set to
resolve them. A run with ocio_config empty therefore still writes those
ACES names, and the generated comp opens with "Bad value for viewerProcess"
and every Read in error ("Invalid LUT selected : ACES - ACEScg") under
plain nuke-default. Interim rule until this is fixed in the script: EITHER
always pass a real ocio_config (never run with it empty), OR set
colorManagement to Nuke and the Read/Write colorspaces to a linear
default by hand in your show config when no studio config exists yet.
Read-back step, every run: open one generated .nk with
nuke -t --safe <script.nk> and assert Read1.error() is False before
calling the run done - a correct node count and correct plate paths do not
prove the comp opens without a colour error. Open follow-up: make
batch_shot_setup.py fall back to a coherent nuke-default colour set
(no ACES names) when ocio_config is empty, instead of leaving the other
keys ACES-specific.
What ships with it
4 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.
- today First seen · 237 lines · 67 tokens per session scan A fca8faaaabaa
nuke-shot-setup is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 67 tokens to every session and 2,904 once invoked, about $0.0003 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…