Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/bbernstein/lacylights-mcp/claude-mdgit clone --depth 1 https://github.com/bbernstein/lacylights-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/bbernstein/lacylights-mcp/claude-md)<a href="https://agentmods.dev/instructions/bbernstein/lacylights-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bbernstein/lacylights-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.01985 | $0.01985 |
| Opus 5 | $0.00992 | $0.00992 |
| Sonnet 5 | $0.00397 | $0.00397 |
| Haiku 4.5 | $0.00198 | $0.00198 |
Grade A, and why
lacylights-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 6d 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 — 226 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 when working with code in this repository.
Project Overview
LacyLights MCP is a Model Context Protocol (MCP) server that enables AI-powered theatrical lighting design. It acts as a bridge between AI assistants (like Claude) and the LacyLights lighting control system, providing natural language control of DMX fixtures, scene generation, and cue management.
Role in LacyLights Ecosystem:
- AI integration layer for the LacyLights system
- Provides 80+ MCP tools for lighting control
- Connects AI assistants to the lacylights-go backend
- Enables natural language scene generation and script analysis
Development Commands
Development
npm run dev # Start dev server with auto-reload (tsx watch)
npm run build # Compile TypeScript to dist/
npm start # Run production build from dist/
Testing
npm test # Run all tests
npm run test:watch # Run tests in watch mode
npm run test:coverage # Generate coverage report
Code Quality
npm run lint # Check for linting errors
npm run lint:fix # Fix auto-fixable linting errors
Architecture
Directory Structure
lacylights-mcp/
├── src/
│ ├── index.ts # Main entry point, MCP protocol handler
│ ├── tools/ # MCP tool implementations
│ │ ├── project-tools.ts # Project CRUD operations
│ │ ├── fixture-tools.ts # Fixture management
│ │ ├── look-tools.ts # Look generation and control
│ │ └── cue-tools.ts # Cue sequence and playback
│ ├── services/ # Core services
│ │ ├── graphql-client-simple.ts # Apollo client for backend
│ │ ├── ai-lighting.ts # OpenAI integration
│ │ └── rag-service-simple.ts # Pattern matching service
│ └── types/
│ └── lighting.ts # TypeScript interfaces
├── tests/ # Test files (mirrors src/)
├── run-mcp.js # MCP client integration wrapper
└── dist/ # Compiled output
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.
- 6d ago First seen · 226 lines · 1,985 tokens per session scan A 8a0c3b7f487f
lacylights-mcp CLAUDE.md is an instructions file published in the GitHub repository bbernstein/lacylights-mcp (14 stars, last pushed 1mo ago), licensed MIT. It adds 1,985 tokens to every session, about $0.0099 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-30.
Other instructions, from other repositories
cml-mcp AGENTS.md
AGENTS.md instructions for xorrkaz/cml-mcp, covering agents.md — cml mcp server, project overview, compatibility goal, repository layout and tool modules (src/cmlmcp/tools/).
brilliant_sdk AGENTS.md
Instructions for brilliantlabsAR/brilliant_sdk, covering brilliant sdk — agent guide, how an app works (the pattern behind everything), minimal reading paths, verify without hardware and testing.
NeoMind CLAUDE.md
Claude Code instructions for camthink-ai/NeoMind, covering neomind — edge ai platform for iot, development commands, ecosystem repositories, extension package contract (.nep) and device type template contract (json).
cad-cae-copilot copilot-instructions.md
Copilot instructions for armpro24-blip/cad-cae-copilot, covering github copilot — aieng workspace and essentials.
phone-mcp CLAUDE.md
Claude Code instructions for premex-ab/phone-mcp, covering claude.md, project overview, build commands, architecture and module layout.
zmk-config AGENTS.md
AGENTS.md instructions for urob/zmk-config, covering customization guide, ground rules, how the multi-board layout works, adding a new board and where to change what.