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/letsagents/aseprite-mcp/claude-mdgit clone --depth 1 https://github.com/letsagents/aseprite-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/letsagents/aseprite-mcp/claude-md)<a href="https://agentmods.dev/instructions/letsagents/aseprite-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/letsagents/aseprite-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 | $0.00195 | $0.00195 |
| Opus 5 | $0.00097 | $0.00097 |
| Sonnet 5 | $0.00039 | $0.00039 |
| Haiku 4.5 | $0.00019 | $0.00019 |
Grade A, and why
aseprite-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 4d 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.
What it actually says
CLAUDE.md
本项目的跨工具指令在 AGENTS.md（Codex / Cursor / Copilot / Gemini 等共用同一份）。Claude Code 通过 import 自动读到全文：
@AGENTS.md
Claude Code 专属
以下操作在其他 MCP 客户端里命令/位置不同（Cursor / Cline / Codex 没有 /mcp 斜杠命令）：
- 配置文件：项目根
.mcp.json（标准 stdio server，command: aseprite-mcp；env.ASEPRITE_PATH指向本机 Aseprite）。其他客户端配置见 README。 - 重连 MCP：改了 server 源码并
npm run build后，Claude Code 用/mcp reconnect让新编译产物生效；其他客户端重启客户端即可。
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.
- 4d ago First seen · 13 lines · 195 tokens per session scan A 1e3233ebe958
aseprite-mcp CLAUDE.md is an instructions file published in the GitHub repository letsagents/aseprite-mcp (0 stars, last pushed 24d ago), licensed MIT. It adds 195 tokens to every session, about $0.0010 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
pixellab-pip GEMINI.md
Instructions for Shilo/pixellab-pip: Use PixelLab Pip when the user asks about PixelLab asset generation, editing, animation, MCP setup, REST v2 integration, website/editor workflows, Aseprite, Pixelorama, legacy v1, bearer-token auth, endpoint choice, SDK coverage, or PixelLab docs.
pixellab-pip AGENTS.md
Instructions for Shilo/pixellab-pip: PixelLab Pip is an unofficial, agent-agnostic PixelLab workflow router shipped as a portable Agent Skill. It teaches coding agents to choose between documented PixelLab MCP tools, REST v2 endpoints, website/editor fallback, Aseprite, Pixelorama, and local asset assembly. The…
ase-deliver AGENTS.md
AGENTS.md instructions for ylty1516/ase-deliver, covering asedeliver — contract for any ai, what this tool is, do this, in order, templates and hard visual rules.
pixel-plugin CLAUDE.md
Instructions for willibrandon/pixel-plugin, covering claude.md, project overview, architecture, directory structure and plugin component specifications.
ase-deliver CLAUDE.md
Claude Code instructions for ylty1516/ase-deliver: Follow AGENTS.md. Compile sprites with python -m asedeliver. The deliverable is always out/ .aseprite.
pixel-mcp CLAUDE.md
Instructions for willibrandon/pixel-mcp, covering claude.md, project overview, build commands, build the server binary and or: go build -o bin/pixel-mcp ./cmd/pixel-mcp.