Borrowing it
Nothing to install: this file belongs to cyanheads/pixoo-mcp-server. 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/cyanheads/pixoo-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/cyanheads/pixoo-mcp-serverWrote 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/cyanheads/pixoo-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/cyanheads/pixoo-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/cyanheads/pixoo-mcp-server/agents-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.04190 | $0.04190 |
| Opus 5 | $0.02095 | $0.02095 |
| Sonnet 5 | $0.00838 | $0.00838 |
| Haiku 4.5 | $0.00419 | $0.00419 |
Grade A, and why
pixoo-mcp-server AGENTS.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.
Copies of this mod
1 near-identical copy found in the catalogue:
- pixoo-mcp-server CLAUDE.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Protocol
Server: pixoo-mcp-server
Version: 1.1.1
Framework: @cyanheads/mcp-ts-core ^0.12.3
Engines: Bun ≥1.3.0, Node ≥24.0.0
MCP SDK: @modelcontextprotocol/server ^2.0.0 (protocol revision 2026-07-28 alongside the 2025 era)
Zod: ^4.4.3
Read the framework docs first:
node_modules/@cyanheads/mcp-ts-core/CLAUDE.mdcontains the full API reference — builders, Context, error codes, exports, patterns. This file covers server-specific conventions only.
Architecture Overview
Local-network MCP server for Divoom Pixoo LED matrix displays (Pixoo-64 primary; 16/32 supported). The server owns all composition — rendering happens in an RGBA canvas pipeline on the host via @cyanheads/pixoo-toolkit, and the device receives final RGB frames over its local HTTP API.
Two distinct layers:
src/renderer/— Pure rendering pipeline with no device dependency. Element renderers, styled-text engine (gradient ramps, shadows, outlines, semantic alignment), theme/palette registry, icon registry, effect compiler (presets → keyframes), keyframe interpolation, preview encoding (PNG/contact-sheet/GIF). Independently unit-testable.src/services/pixoo/—PixooServicewraps@cyanheads/pixoo-toolkit. Handles lazy init from config, command serialization with min-interval pacing,ensureCustomChannel(), result→error-contract mapping, and device state snapshots.
Tools call renderer + service; they don't talk to the toolkit directly.
What's Next?
When the user asks what's next or needs direction, suggest options based on the current project state. Common next steps:
- Re-run the
setupskill — ensures CLAUDE.md, skills, structure, and metadata are populated and up to date - Add tools/resources/prompts — scaffold new definitions using the
add-tool,add-resource,add-promptskills - Field-test definitions — exercise tools/resources/prompts with real inputs using the
field-testskill - Run
devcheck— lint, format, typecheck, and security audit - Run the
security-passskill — audit handlers for MCP-specific security gaps: output injection, scope blast radius, input sinks, tenant isolation - Run the
polish-docs-metaskill — finalize README, CHANGELOG, metadata, and agent protocol for shipping - Run the
maintenanceskill — investigate changelogs, adopt upstream changes, and sync skills afterbun update --latest
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 · 325 lines · 4,190 tokens per session scan A d78c7325c10a
pixoo-mcp-server AGENTS.md is an instructions file published in the GitHub repository cyanheads/pixoo-mcp-server (8 stars, last pushed 16d ago), licensed Apache-2.0. It adds 4,190 tokens to every session, about $0.0209 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
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).
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.
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.
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).
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.