fusion-spatial-mcp: Instructions file for Claude Code

CLAUDE.md

fusion-spatial-mcp CLAUDE.md is an instructions file for Claude Code from aphollis/fusion-spatial-mcp. It costs 427 tokens per session, scanned A, original, MIT.

Project instructions for building fusion-spatial-mcp, a tool that connects an AI agent to Autodesk Fusion design software for spatial and 3D work.

In plain words
What is it for?
Use them to follow the project's build plan, keep Fusion-specific concepts and units correct, and avoid running generated code in a user's live session without approval.
Why use it?
They impose a required build order and warn about project-specific rules, API units, and safe testing with a live Fusion session.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is aphollis/fusion-spatial-mcp's own configuration. It tells Claude Code how to work on fusion-spatial-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything fusion-spatial-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to aphollis/fusion-spatial-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/aphollis/fusion-spatial-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/aphollis/fusion-spatial-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.

agentmods badge for fusion-spatial-mcp CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/aphollis/fusion-spatial-mcp/claude-md/github.svg)](https://agentmods.dev/instructions/aphollis/fusion-spatial-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/aphollis/fusion-spatial-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/aphollis/fusion-spatial-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.

agentmods 80×15 button for fusion-spatial-mcp CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/aphollis/fusion-spatial-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/aphollis/fusion-spatial-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 427 This file is loaded in full into every session.
When invoked 427 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00427 $0.00427
Opus 5.5 $0.00171 $0.00171
Sonnet 5.5 $0.00085 $0.00085
Haiku 4.5 $0.00043 $0.00043

Measured 2mo ago against content hash 69aae7e7291b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

fusion-spatial-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 2mo 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 · 30 lines

What it actually says

fusion-spatial-mcp — session context

Read docs/BUILD_PLAN.md FIRST — it is the authoritative, self-contained plan with milestones, acceptance gates, Fusion-specific traps, and pointers into the reference implementation. Follow its phase order (F0→F5); do not write spatial tool code before the F2 conformance gate passes.

Hard rules:

  • Design Fusion-native. This project is not a port of the Rhino server: tool vocabulary, workflows, and agent guidance come from Fusion's own concepts (timeline, features, constrained sketches, user parameters, components). The sibling checkout ../rhino-gh-mcp is an infrastructure donor only: a source of engineering patterns (TCP bridge, threading, token efficiency). spatial-core lives in its own sibling repo ../spatial-core (consumed via file: dependency — never fork/copy its source). Do not carry Grasshopper concepts or names across.
  • Never run generated code against the user's live Fusion session without asking first. Compile-check offline; batch live testing into agreed steps.
  • Fusion API traps: internal units are ALWAYS centimeters (convert to the design's default display unit at the adapter); documents are commonly Y-up (report the actual axis); use entityToken as body id; API calls only on the main thread via CustomEvent marshaling; listener binds WITHOUT SO_REUSEADDR.
  • This repo is public — no machine-specific paths or private details in committed files. Machine tooling notes live in session memory, not here. Validate add-in Python offline with any CPython 3.9+ py_compile.
  • Fusion 360 is installed (webdeploy production). Dev add-ins folder: %APPDATA%\Autodesk\Autodesk Fusion 360\API\AddIns\ (user has prior add-in experience — "Sheeter" add-in and the FusionRhinoBar project).
  • Commit per milestone with concise messages; push to origin (public repo).
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.

  1. 2mo ago First seen · 30 lines · 427 tokens per session scan A 69aae7e7291b

Subscribe to this mod's changes

fusion-spatial-mcp CLAUDE.md is an instructions file published in the GitHub repository aphollis/fusion-spatial-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 427 tokens to every session, about $0.0017 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.

Related

fusion-spatial-mcp CLAUDE.md compared with instructions from other repositories

fusion-spatial-mcp CLAUDE.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
fusion-spatial-mcp CLAUDE.mdaphollis/fusion-spatial-mcpInstructions file03mo agoMITA427Claude Code
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode