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 ifBars/blender-agent-studio --skill blender-procedural-workflowgit clone --depth 1 https://github.com/ifBars/blender-agent-studioWrote 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/ifbars/blender-agent-studio/blender-procedural-workflow)<a href="https://agentmods.dev/skills/ifbars/blender-agent-studio/blender-procedural-workflow"><img src="https://agentmods.dev/badge/skills/ifbars/blender-agent-studio/blender-procedural-workflow.svg" alt="Measured on agentmods" 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.00580 |
| Opus 5 | $0.00028 | $0.00290 |
| Sonnet 5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
blender-procedural-workflow 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blender Procedural Workflow
Read the shared execution guidance once per task for autonomous decisions, evidence cadence, and long-task continuity.
Build an editable generator with an explicit parameter contract, not a one-off node graph that only works for its current input.
Define the generator contract
Identify inputs, units, random seed, variation controls, source assets, performance budget, expected output geometry, and what the user may safely change. State invariants such as non-overlap, terrain conformity, cardinal orientation, density limits, stable IDs, or export realization.
Name node groups, sockets, modifiers, collections, materials, and instances semantically. Keep input assets separate from generated output and do not hide critical behavior in unnamed internal values.
Author in layers
- Start with a minimal graph proving the major transformation or placement rule. Test its output from multiple views before adding variation.
- Expose only meaningful controls at the group interface, with units, ranges, defaults, and clear names. Keep dependent constants in the durable Python source where agents can regenerate them.
- Use deterministic seed handling. When instances must remain stable across revisions, derive randomness from stable element IDs rather than evaluation order.
- Prefer instancing for repeated assets; realize instances only for operations or exports that require real geometry. Measure evaluated triangle counts and memory implications after realization.
- For terrain/scatter systems, validate slope, normal alignment, collision or exclusion zones, density falloff, scale range, clipping, and silhouette.
- For modifiers and node graphs that feed animation or simulation, define the evaluation order and cache/bake boundary explicitly.
Test the parameter surface
Render and inspect the default, minimum, maximum, and at least one seeded variation. Test empty/small and dense/large inputs where meaningful. A graph that looks good at a single seed or density is not reusable.
What ships with it
2 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 Changed · +3 lines f78919e2e9a9
- 8d ago First seen · 56 lines · 56 tokens per session scan A f6122a316fc2
blender-procedural-workflow is a skill published in the GitHub repository ifBars/blender-agent-studio (14 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 580 once invoked, about $0.0003 per session on Opus 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-08-31.
Other skills, from other repositories
dcc-mcp-blender-setup
Set up dcc-mcp-blender for an agent or operator: install Blender Python dependencies with Blender's bundled interpreter, install a startup bridge, generate MCP host configuration, and run a first live-tool smoke prompt.
blender-import-to-scene
Blender cross-DCC asset import skill — consumes an AssetDescriptor, opens the asset file in Blender, and returns an ImportToSceneResult. Use as the receiving end of the asset import pipeline after an asset-source skill resolves the descriptor.
blender-physics
Blender rigid body, soft body, cloth, collision, force fields, particle systems, constraints, and simulation cache tools.
blender-interchange
Blender interchange skill for typed FBX/OBJ/USD imports, GLTF/USD/Alembic exports, and repeatable batch exports. Use for moving assets between DCC, game, and pipeline tools before falling back to scripting.
blender-scene-assembly
Blender scene assembly — merge .blend files, append/link data blocks, manage view layers and external references.
blender-asset-source
Blender asset source discovery — search filesystem and asset libraries for importable 3D assets.