pixso-mcp: Instructions file for Claude Code

CLAUDE.md

pixso-mcp CLAUDE.md is an instructions file for Claude Code from TheAlmightyMight/pixso-mcp. It costs 1,532 tokens per session, scanned A, original, MIT.

Project instructions for Pixso MCP Server, a bridge between coding agents and Pixso design files using the Model Context Protocol. They cover the Node.js server, Pixso plugin, commands, and development checks.

In plain words
What is it for?
They are for developing, testing, type-checking, debugging exports, and running the Pixso MCP server and plugin.
Why use it?
They explain how the repository is structured and how its server and plugin communicate. This gives an agent the context needed to run checks and diagnose export or integration issues.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is TheAlmightyMight/pixso-mcp's own configuration. It tells Claude Code how to work on pixso-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 pixso-mcp configures →

Reuse

Borrowing it

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thealmightymight/pixso-mcp/claude-md.svg)](https://agentmods.dev/instructions/thealmightymight/pixso-mcp/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/thealmightymight/pixso-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/thealmightymight/pixso-mcp/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 1,532 This file is loaded in full into every session.
When invoked 1,532 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.01532 $0.01532
Opus 5 $0.00766 $0.00766
Sonnet 5 $0.00306 $0.00306
Haiku 4.5 $0.00153 $0.00153

Measured 7d ago against content hash 43ecdc47e869, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

pixso-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 7d 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 · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 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.

Project Overview

Pixso MCP Server — a bridge that lets LLMs (e.g., Claude) interact with Pixso design files via the Model Context Protocol. The project has two parts that communicate over WebSocket (port 3667):

  1. MCP Server (server/) — Node.js server using @modelcontextprotocol/sdk, communicates with MCP clients via Streamable HTTP (port 3668, endpoint /mcp) and with the Pixso plugin via WebSocket (port 3667).
  2. Pixso Plugin (plugin/) — runs inside Pixso; ui.html maintains the WebSocket connection, main.js handles commands in the plugin's main thread using the pixso API.

Commands

npm start              # Run the MCP server (node server/index.js)
npm run lint:all       # ESLint across the project
npm run typecheck      # TypeScript type checking (tsc)
npm run count-tokens   # Count tokens in get_selection response
npm run debug-export   # Diagnose export tools — validates PNG/SVG pipeline
npm run dev            # Run test app in __tests__/test-app

No build step — all source files are plain JS (ES modules, "type": "module"). TypeScript is used only for type-checking via JSDoc annotations.

Project Structure

server/
  index.js          — MCP server entry point, wires bridge + tool handlers
  bridge.js         — WebSocket bridge: lane-based queuing, callPlugin()
  tools.js          — MCP tool definitions (get_selection, get_selection_png, get_selection_svg, diagnose_export)
plugin/
  main.js           — Pixso plugin main thread (sandbox, single-file, 650+ lines)
  ui.html           — WebSocket client UI with auto-reconnect, status & stats
  manifest.json     — Pixso plugin manifest
tokens.js           — статистика токенов для ответа MCP сервера
count-tokens.js     — утилита: запрашивает выделение и считает токены
debug-export.js     — утилита: диагностика экспорта PNG/SVG
property-flags.md   — Pixso property → serialization flag mapping (A/P/C/N)
__tests__/
  test-app/         — Vite + React app for codegen testing
  test_results/     — output directory for test results
docs/               — planning and design spec documents

Read the full file on GitHub · 102 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.

  1. 7d ago First seen · 102 lines · 1,532 tokens per session scan A 43ecdc47e869

Subscribe to this mod's changes

pixso-mcp CLAUDE.md is an instructions file published in the GitHub repository TheAlmightyMight/pixso-mcp (0 stars, last pushed 5mo ago), licensed MIT. It adds 1,532 tokens to every session, about $0.0077 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-09-01.

Related

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.

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

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens