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.
git clone --depth 1 https://github.com/bitqs/SlimeWrote 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/plugins/bitqs/slime/slime)<a href="https://agentmods.dev/plugins/bitqs/slime/slime"><img src="https://agentmods.dev/badge/plugins/bitqs/slime/slime/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/plugins/bitqs/slime/slime"><img src="https://agentmods.dev/badge/plugins/bitqs/slime/slime.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 1mo 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
{
"name": "slime",
"description": "Your work goals are the bosses. Your plugins are your gear. Watch Claude fight — a zero-impact RPG layer over Claude Code.",
"author": { "name": "qs", "url": "https://github.com/bitqs" },
"repository": "https://github.com/bitqs/slime",
"homepage": "https://github.com/bitqs/slime",
"license": "MIT",
"keywords": ["claude-code", "statusline", "hud", "hooks", "gamification", "rpg", "game", "tmux", "token-usage", "pixijs", "fun"]
}
What it installs
The manifest is a name and a version. 13 commands, 9 hooks travel with it, and installing the plugin installs all of them — 201 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Command setup A 23 tokens
- Command stream A 17 tokens
- Command arena A 11 tokens
- Command prestige A 16 tokens
- Command replay A 27 tokens
- Command gear A 24 tokens
- Command achievements A 12 tokens
- Command battlelog A 6 tokens
- Command bestiary A 16 tokens
- Command milestones A 11 tokens
- Command oracle A 18 tokens
- Command wrapped A 13 tokens
- Command update A 7 tokens
- Hook PreToolUse A not measured
- Hook Stop A not measured
- Hook PostToolUseFailure A not measured
- Hook UserPromptSubmit A not measured
- Hook SubagentStart A not measured
- Hook SessionStart A not measured
- Hook PostToolUse A not measured
- Hook SubagentStop A not measured
- Hook PreCompact A not measured
What ships with it
1 file beside plugin.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.
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.
- 1mo ago First seen · 10 lines scan A 7ca15a39ad5a
slime is a plugin published in the GitHub repository bitqs/Slime (1 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
hush
Quieter sessions for Claude Code: less narration, shorter tool output and concise answers focused on the result.
breakwatch
Streak-aware break reminders. Hooks log work streaks across every project without the model having to remember anything; when a streak runs long the nudge arrives as an OS notification and asks rather than asserts. Thresholds are time-of-day weighted and retune themselves against a target nudge rate, under floors that.
rate-limit-monitor
Statusline segment + prompt-submit guard for Claude Code's 5-hour and 7-day usage limits. Shows live usage %, and at a configurable threshold it blocks new prompts (with an override) so a long token-heavy task doesn't get cut off mid-run.
notifications
Sound + desktop notifications when Claude Code needs your attention or finishes a task (Linux & macOS).
claude-pet
A desktop pet that grows as you code with Claude Code — read-only state engine, Electron widget, reminders, and achievements.
notify
Windows toast notifications and sound effects for Claude Code. Notifies on permission requests and task completion.