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.
curl -O https://raw.githubusercontent.com/TheAlmightyMight/pixso-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/TheAlmightyMight/pixso-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/thealmightymight/pixso-mcp/claude-md)<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>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.01532 | $0.01532 |
| Opus 5 | $0.00766 | $0.00766 |
| Sonnet 5 | $0.00306 | $0.00306 |
| Haiku 4.5 | $0.00153 | $0.00153 |
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.
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):
- 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). - Pixso Plugin (
plugin/) — runs inside Pixso;ui.htmlmaintains the WebSocket connection,main.jshandles commands in the plugin's main thread using thepixsoAPI.
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
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.
- 7d ago First seen · 102 lines · 1,532 tokens per session scan A 43ecdc47e869
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.
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.