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 blender-compositinggit 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/blender-compositing)<a href="https://agentmods.dev/skills/sideshowroberto/vfx-agent-toolkit/blender-compositing"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/blender-compositing/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/blender-compositing"><img src="https://agentmods.dev/badge/skills/sideshowroberto/vfx-agent-toolkit/blender-compositing.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.00056 | $0.03182 |
| Opus 5.5 | $0.00022 | $0.01273 |
| Sonnet 5.5 | $0.00011 | $0.00636 |
| Haiku 4.5 | $0.00006 | $0.00318 |
Grade A, and why
blender-compositing 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 — 384 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blender Compositing Skill
Version: 3.0.0 Last Updated: 2026-06-15 Dependencies: Blender 5.1+
Breaking Changes (5.1+)
Compositor Node Tree Access Changed
scene.node_tree no longer exists. Use scene.compositing_node_group instead. Must create the node group manually if None.
import bpy
scene = bpy.context.scene
scene.use_nodes = True
# [FAIL] BROKEN in 5.1+
# compositor = scene.node_tree
# [OK] Access or create compositor node group
comp_tree = scene.compositing_node_group
if comp_tree is None:
comp_tree = bpy.data.node_groups.new(name="Compositor", type='CompositorNodeTree')
scene.compositing_node_group = comp_tree
scene.render.use_compositing = True
CompositorNodeComposite Removed
There is no Composite output node in 5.1+. The main render output comes directly from the render pipeline (set via scene.render.filepath and scene.render.image_settings). Use CompositorNodeViewer for preview and CompositorNodeOutputFile for additional outputs.
import bpy
# [FAIL] BROKEN in 5.1+ (RuntimeError: Node type undefined)
# composite = nodes.new('CompositorNodeComposite')
# [OK] Main render output is controlled by scene.render settings
scene = bpy.context.scene
scene.render.filepath = "//output/render_"
scene.render.image_settings.file_format = 'PNG'
# [OK] Use Viewer for compositor preview
viewer = comp_tree.nodes.new('CompositorNodeViewer')
CompositorNodeMapRange Removed
No Map Range node in the compositor. Use ShaderNodeMath (works in compositor context) to build equivalent logic.
import bpy
# [FAIL] BROKEN in 5.1+
# map_range = comp_tree.nodes.new('CompositorNodeMapRange')
# [OK] Use Math nodes for range mapping
# Example: clamp depth to max 80m, then normalize
clamp = comp_tree.nodes.new('ShaderNodeMath')
clamp.operation = 'MINIMUM'
clamp.inputs[1].default_value = 80.0
normalize = comp_tree.nodes.new('CompositorNodeNormalize')
comp_tree.links.new(rl.outputs['Depth'], clamp.inputs[0])
comp_tree.links.new(clamp.outputs[0], normalize.inputs[0])
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 · 384 lines · 56 tokens per session scan A 17d8aa201fad
blender-compositing is a skill published in the GitHub repository sideshowroberto/vfx-agent-toolkit (16 stars, last pushed 22d ago), licensed MIT. It adds 56 tokens to every session and 3,182 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…