slime

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

slime 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.

.claude-plugin/marketplace.json · 18 lines

What it actually says

{
  "name": "slime",
  "owner": { "name": "qs" },
  "plugins": [
    {
      "name": "slime",
      "source": "./",
      "displayName": "Slime — your coding session as an RPG",
      "description": "Turn your real Claude Code session into a turn-based RPG: a statusline HUD + a PixiJS browser arena render your goals as bosses, your todos as minions, and your token budget as your resource — gamification, hooks, tmux, zero impact on the session.",
      "category": "Learning",
      "homepage": "https://github.com/bitqs/slime",
      "author": { "name": "qs", "url": "https://github.com/bitqs" },
      "license": "MIT",
      "keywords": ["claude-code", "statusline", "hud", "hooks", "gamification", "rpg", "game", "tmux", "token-usage", "pixijs", "fun"]
    }
  ]
}

Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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