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 HitamLegit6777/blender-mcp-ultra --skill blender-pro-workflowgit clone --depth 1 https://github.com/HitamLegit6777/blender-mcp-ultraWrote 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/hitamlegit6777/blender-mcp-ultra/blender-pro-workflow)<a href="https://agentmods.dev/skills/hitamlegit6777/blender-mcp-ultra/blender-pro-workflow"><img src="https://agentmods.dev/badge/skills/hitamlegit6777/blender-mcp-ultra/blender-pro-workflow/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/hitamlegit6777/blender-mcp-ultra/blender-pro-workflow"><img src="https://agentmods.dev/badge/skills/hitamlegit6777/blender-mcp-ultra/blender-pro-workflow.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.00000 | $0.00504 |
| Opus 5 | $0.00000 | $0.00252 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
blender-pro-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 11d 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.
What it actually says
blender-pro-workflow — Professional Production Workflow
Multi-phase production workflow for professional 3D asset creation.
Phase 1: Brief & Planning
- Understand the deliverable (format, poly count, texture resolution)
- Gather references (images, sketches, dimensions)
- Plan naming convention:
GEO_,MAT_,LGT_,CAM_,TEX_,COL_
Phase 2: Block-out
Goal: Rough proportions and composition
- Use simple primitives at correct scale
- Focus on silhouette and proportions
- Set up camera angle
- Present block-out for approval
Phase 3: High-Poly Modeling
Goal: Detailed mesh with proper topology
- Add edge loops for support
- Apply bevels and subdivisions
- Boolean operations for cuts
- Check mesh quality with mesh_analysis()
Phase 4: UV & Texturing
Goal: Proper UV layout and PBR materials
- Unwrap with smart project or manual seams
- Ensure UVs are within 0-1 space
- Apply PBR materials
- Bake if needed
Phase 5: Look-Dev
Goal: Final appearance with lighting and materials
- Set up three-point or environment lighting
- Fine-tune material values
- Add camera DOF if needed
- Validate with screenshot
Phase 6: Export & Delivery
Goal: Clean, optimized deliverable
- Apply all transforms
- Purge orphan data
- Name everything consistently
- Export in requested format
- Verify exported file
Naming Convention
| Prefix | Type | Example |
|---|---|---|
| GEO_ | Geometry | GEO_Sword_Blade |
| MAT_ | Material | MAT_Gold_01 |
| LGT_ | Light | LGT_Key_Top |
| CAM_ | Camera | CAM_Hero_Shot |
| TEX_ | Texture | TEX_Brick_Wall |
| COL_ | Collection | COL_Props |
Validation Gates
Each phase must pass before moving to next:
- Block-out: ✅ Proportions match reference
- Modeling: ✅ Manifold, no N-gons, clean topology
- UV: ✅ No overlaps, efficient packing
- Look-Dev: ✅ Matches reference lighting
- Export: ✅ File opens correctly in target app
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.
- 11d ago First seen · 81 lines · 0 tokens per session scan A 6ed43df1cf4e
blender-pro-workflow is a skill published in the GitHub repository HitamLegit6777/blender-mcp-ultra (1 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 504 tokens. 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…