What is retopoflow_blender_mcp CLAUDE.md?

A set of project instructions for developing a Blender add-on and its related MCP server. It defines the project layout, documentation locations, and a behavior-driven development workflow, where features are described and tested from expected behavior.

Use it when modifying the Blender MCP project, adding tools, writing behavior-driven tests, or creating patch notes.

It keeps tools, tests, feature descriptions, and release notes organized in the expected places. It also provides project-specific rules for adding tools and recording changes.

How ShirshovDIM/retopoflow_blender_mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to ShirshovDIM/retopoflow_blender_mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/ShirshovDIM/retopoflow_blender_mcp/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/ShirshovDIM/retopoflow_blender_mcp

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/shirshovdim/retopoflow_blender_mcp/claude-md/github.svg)](https://agentmods.dev/instructions/shirshovdim/retopoflow_blender_mcp/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/shirshovdim/retopoflow_blender_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/shirshovdim/retopoflow_blender_mcp/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/shirshovdim/retopoflow_blender_mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/shirshovdim/retopoflow_blender_mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 589 This file is loaded in full into every session.

When invoked 589 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00589	$0.00589
Opus 5	$0.00295	$0.00295
Sonnet 5	$0.00118	$0.00118
Haiku 4.5	$0.00059	$0.00059

Measured 10d ago against content hash 81b58875d3a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

retopoflow_blender_mcp CLAUDE.md 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 10d 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.

CLAUDE.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blender MCP - Agent Guidelines

Project Structure

blender-mcp/
├── addon.py                    # Blender addon with socket server
├── src/
│   ├── server.py               # MCP server with @mcp.tool() decorators
│   ├── tools/                  # Tools layer (formatting & validation)
│   ├── blender_handlers/       # Handler layer (Blender API calls)
│   ├── prompts/                # MCP prompts
│   └── retopo_tools/           # Retopology-specific tools
├── features/                   # BDD Gherkin feature files
├── tests/                      # pytest-bdd tests
└── patch_notes/                # Release notes and summaries

Documentation Rules

Patch Notes Location

All patch notes, summaries, and release documentation MUST be placed in:

./patch_notes/

File naming convention:

YYYY-MM-DD_<description>.md

Examples:

2025-12-08_api_optimization_for_retopo_agent.md
2025-12-06_features_28-31_test_report.md

DO NOT place patch notes in ./docs/ or other locations.

Development Workflow

Adding New Tools (BDD-First)

Create BDD feature file in features/XX_tool_name.feature
Copy to agent repo: D:\repos\agent_retopologist\features\
Implement handler in src/blender_handlers/ module
Update __init__.py exports
Add to addon.py: import, handler dict, method
Add tools layer in src/tools/
Register in src/server.py: import and @mcp.tool()

Three-Layer Architecture

src/server.py           (@mcp.tool decorator - MCP interface)
       ↓
src/tools/*.py          (Tools layer - formatting & validation)
       ↓
src/blender_handlers/*  (Handler layer - Blender API calls)
       ↓
addon.py                (Socket server running in Blender)

Testing

Run tests: python -m pytest tests/
Verify syntax: python -m py_compile <file>
DO NOT write tests for new features unless explicitly requested

Feature Files Sync

BDD feature files must be synced to the agent repository:

Source: D:\repos\blender-mcp\features\
Target: D:\repos\agent_retopologist\features\

Read the full file on GitHub · 82 lines

Changes

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.

10d ago First seen · 82 lines · 589 tokens per session scan A 81b58875d3a4

Subscribe to this mod's changes

retopoflow_blender_mcp CLAUDE.md is an instructions file published in the GitHub repository ShirshovDIM/retopoflow_blender_mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 589 tokens to every session, about $0.0029 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.

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

retopoflow_blender_mcp: Instructions file for Claude Code