Borrowing it
Nothing to install: this file belongs to lesleslie/spline-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.
curl -O https://raw.githubusercontent.com/lesleslie/spline-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/lesleslie/spline-mcpWrote 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/instructions/lesleslie/spline-mcp/claude-md)<a href="https://agentmods.dev/instructions/lesleslie/spline-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/lesleslie/spline-mcp/claude-md.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.01010 | $0.01010 |
| Opus 5 | $0.00505 | $0.00505 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
spline-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 3d 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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
For a shorter, tool-neutral bootstrap document, start with AGENTS.md.
Project Overview
Spline MCP Server is a Model Context Protocol server for orchestrating Spline.design 3D scenes. It provides tools for managing 3D objects, materials, events, and runtime state.
Ecosystem Context
Part of the Bodai Ecosystem:
| Component | Role | Port |
|---|---|---|
| Mahavishnu | Orchestrator | 8680 |
| Akosha | Seer | 8682 |
| Dhara | Curator | 8683 |
| Session-Buddy | Builder | 8678 |
| Crackerjack | Inspector | 8676 |
| spline-mcp | 3D Orchestrator | 3052 |
Development Commands
Setup
uv venv
source .venv/bin/activate
uv pip install -e ".[dev]"
Testing
pytest
pytest --cov=spline_mcp --cov-report=html
Code Quality
ruff format spline_mcp/
ruff check spline_mcp/
mypy spline_mcp/
MCP Server
# Stdio mode
spline-mcp serve
# HTTP mode
spline-mcp serve --http --port 3052
# Health check
spline-mcp health
Architecture
spline_mcp/
├── __init__.py # Package metadata
├── cli.py # Typer CLI commands
├── config.py # Oneiric-based configuration
├── server.py # FastMCP application
├── client.py # Spline API client (placeholder)
├── assets/ # Asset management
├── generators/ # Code generation (React, Vanilla, Next.js)
├── integrations/ # External integrations
└── tools/ # MCP tool definitions
├── __init__.py # Tool registration helpers
├── generation.py # Code generation tools (6)
├── assets.py # Asset management tools (5)
├── helpers.py # Utility tools (5)
├── integration.py # Integration tools (6)
└── docs.py # Documentation tools (3)
Key Patterns
Oneiric Configuration
Settings loaded from:
- Default values in
SplineSettings settings/spline-mcp.yamlsettings/local.yaml(gitignored)- Environment variables
SPLINE_*
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.
- 3d ago Changed aa71628ae430
- 8d ago First seen · 145 lines · 1,010 tokens per session scan A 92dc4418df45
spline-mcp CLAUDE.md is an instructions file published in the GitHub repository lesleslie/spline-mcp (4 stars, last pushed 7d ago), licensed BSD-3-Clause. It adds 1,010 tokens to every session, about $0.0051 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 instructions, from other repositories
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.
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.
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).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.