pixel-setup

A setup command for connecting the pixel-mcp server to Aseprite, an application for drawing and animating pixel art.

In plain words
What is it for?
It helps detect Aseprite, create its configuration, verify the executable, test communication, and report errors or version information.
Why use it?
It avoids manually locating the Aseprite program and checking whether the server connection works.

Command

Install

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.

agentmods
npx agentmods add commands/willibrandon/pixel-plugin/pixel-setup
Clone the repo
git clone --depth 1 https://github.com/willibrandon/pixel-plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,958 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.01958
Opus 5 $0.00005 $0.00979
Sonnet 5 $0.00002 $0.00392
Haiku 4.5 $0.00001 $0.00196

Measured yesterday against content hash cd0ded62e400, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pixel-setup 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 yesterday.

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.

commands/pixel-setup.md · 273 lines

How it starts

The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/pixel-setup - Plugin Configuration

Configure the pixel-mcp server and verify Aseprite installation.

Usage

/pixel-setup [aseprite-path]

Arguments

aseprite-path (optional): Path to Aseprite executable

  • If not provided, attempts auto-detection
  • If detection fails, prompts user for path

What This Command Does

  1. Detects Aseprite installation

    • Searches common installation paths for current platform
    • macOS: /Applications/Aseprite.app/Contents/MacOS/aseprite
    • Linux: /usr/bin/aseprite, /usr/local/bin/aseprite
    • Windows: C:\Program Files\Aseprite\Aseprite.exe
  2. Creates configuration file

    • Generates ~/.config/pixel-mcp/config.json (macOS/Linux)
    • Generates %APPDATA%\pixel-mcp\config.json (Windows)
    • Sets aseprite_path in configuration
  3. Validates configuration

    • Tests that Aseprite executable exists and is executable
    • Verifies pixel-mcp can communicate with Aseprite
    • Reports version information
  4. Tests MCP server

    • Runs health check on pixel-mcp server
    • Confirms tools are accessible
    • Reports success or errors

Examples

/pixel-setup
→ Auto-detects Aseprite installation and configures

/pixel-setup /Applications/Aseprite.app/Contents/MacOS/aseprite
→ Uses specified path for macOS

/pixel-setup "C:\Program Files\Aseprite\Aseprite.exe"
→ Uses specified path for Windows

/pixel-setup /usr/local/bin/aseprite
→ Uses specified path for Linux

Auto-Detection Paths

macOS:

  • /Applications/Aseprite.app/Contents/MacOS/aseprite
  • $HOME/Applications/Aseprite.app/Contents/MacOS/aseprite
  • /usr/local/bin/aseprite
  • $HOME/.local/bin/aseprite

Linux:

  • /usr/bin/aseprite
  • /usr/local/bin/aseprite
  • $HOME/.local/bin/aseprite
  • $HOME/bin/aseprite
  • /opt/aseprite/bin/aseprite
  • /snap/bin/aseprite

Windows:

  • C:\Program Files\Aseprite\Aseprite.exe
  • C:\Program Files (x86)\Aseprite\Aseprite.exe
  • %LOCALAPPDATA%\Aseprite\Aseprite.exe
  • %USERPROFILE%\AppData\Local\Aseprite\Aseprite.exe

Read the full file on GitHub · 273 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. yesterday First seen · 273 lines · 11 tokens per session scan A cd0ded62e400

Subscribe to this mod's changes

pixel-setup is a command published in the GitHub repository willibrandon/pixel-plugin (302 stars, last pushed 10mo ago), licensed MIT. It adds 11 tokens to every session and 1,958 once invoked, about $0.0001 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.