retro-diffusion

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.

Security

Grade A, and why

retro-diffusion 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 2d 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.

.claude-plugin/marketplace.json · 27 lines

What it actually says

{
  "name": "retro-diffusion",
  "owner": {
    "name": "Astropulse",
    "url": "https://retrodiffusion.ai"
  },
  "metadata": {
    "description": "Real pixel art generation for AI assistants — sprites, animations, and tilesets by Retro Diffusion",
    "version": "1.0.0"
  },
  "plugins": [
    {
      "name": "pixel-art",
      "source": "./plugins/pixel-art",
      "description": "Generate authentic pixel art — sprites, animations, tilesets — via the hosted Retro Diffusion MCP server, with a workflow skill for cost-aware, game-ready results",
      "author": {
        "name": "Astropulse",
        "url": "https://retrodiffusion.ai"
      },
      "homepage": "https://github.com/Retro-Diffusion/retro-diffusion-mcp",
      "license": "MIT",
      "keywords": ["pixel-art", "game-assets", "sprites", "animation", "tileset", "image-generation", "gamedev"],
      "category": "creative"
    }
  ]
}

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.

Related

Other plugins, from other repositories