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 GoogilyBoogily/googilyboogily-claude-power-tools --skill blender-pythongit clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-toolsWrote 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/googilyboogily/googilyboogily-claude-power-tools/blender-python)<a href="https://agentmods.dev/skills/googilyboogily/googilyboogily-claude-power-tools/blender-python"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/blender-python/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/googilyboogily/googilyboogily-claude-power-tools/blender-python"><img src="https://agentmods.dev/badge/skills/googilyboogily/googilyboogily-claude-power-tools/blender-python.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.00240 | $0.03163 |
| Opus 5.5 | $0.00096 | $0.01265 |
| Sonnet 5.5 | $0.00048 | $0.00633 |
| Haiku 4.5 | $0.00024 | $0.00316 |
Grade A, and why
blender-python 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 1mo ago.
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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blender Python API
Drive Blender via its embedded Python interpreter (bpy). Covers GUI scripting, headless --background automation, addon authoring, the bpy-as-pip-module path, and live MCP control. Reference files in references/ deepen each area — load on demand, not all at once.
Operating Principles
-
Work through the data API, not operators, when possible.
bpy.ops.*calls depend on context (active area, mode, selection). They fail withRuntimeError: poll() failed, context is incorrectfrom scripts. Direct manipulation throughbpy.data.objects["Cube"].location.z = 1.0is faster, deterministic, and works headless. Use operators only when the data API has no equivalent (e.g., complex modeling tools, file I/O wrappers). -
Identify the target environment first. Three execution modes — pick one before writing code:
- Inside Blender GUI — Text Editor / Python Console. Full context, full UI redraws.
- Headless
--background—blender file.blend -b -P script.py. No UI, no event loop. Modal operators don't run, redraws don't happen, viewport context is empty. - bpy as Python module —
pip install bpy, thenimport bpyfrom any script. Behaves like--background --factory-startup. Same headless caveats.
-
Match the Blender version. API breaks across major versions. Blender 4.x changed animation slots/layers, geometry nodes interfaces, and the OBJ/STL operators (now
bpy.ops.wm.obj_export/obj_import, notexport_scene.obj). When the user states a version, match it; otherwise default to Blender 4.5 LTS and confirm. -
Read the source for poll failures. When an operator refuses to run, check
bpy.ops.foo.bar.poll()first. IfFalse, the fix is usually abpy.context.temp_override(...)block or switching to data-API equivalents. Seereferences/gotchas.md. -
Don't auto-overwrite the user's
.blendfile. Always confirm beforebpy.ops.wm.save_mainfile()against the original path. Prefersave_as_mainfile(filepath=..., copy=True).
What ships with it
9 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.
- 1mo ago First seen · 195 lines · 240 tokens per session scan A c8865eaaa55b
blender-python is a skill published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 5mo ago), licensed MIT. It adds 240 tokens to every session and 3,163 once invoked, about $0.0010 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…