agentmods.dev

setup

setup is a command for Claude Code from bitqs/Slime. It costs 23 tokens per session (464 once invoked), scanned A, original, MIT.

A command for installing the Slime statusline HUD, a small live display in Claude Code showing session information.

In plain words
What is it for?
Use it to inspect existing statusline settings, add Slime's display without overwriting custom refresh settings, and enable live updates after restarting Claude Code.
Why use it?
It offers a manual setup path when the automatic installation does not add the display or when the user wants to configure it directly.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the slime plugin — 13 commands, 9 hooks shipped together

not rated 1repo changed 3d ago A scan 23 tokens original MIT

Good fit Use it to inspect existing statusline settings, add Slime's display without overwriting custom refresh settings, and enable live updates after restarting Claude Code.

Compare 6 commands from other repositories ↓
View source ↗ bitqs/Slime slime-arena-demo.shuangqu.workers.dev
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bitqs/Slime
Claude Code
/plugin install slime

Made for: Claude Code.

Or install slime, the plugin that ships this one along with the rest of its 13 commands, 9 hooks.

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

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/bitqs/slime/setup/github.svg)](https://agentmods.dev/commands/bitqs/slime/setup)
Your own site
<a href="https://agentmods.dev/commands/bitqs/slime/setup"><img src="https://agentmods.dev/badge/commands/bitqs/slime/setup/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/bitqs/slime/setup"><img src="https://agentmods.dev/badge/commands/bitqs/slime/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00023 $0.00464
Opus 5.5 $0.00009 $0.00186
Sonnet 5.5 $0.00005 $0.00093
Haiku 4.5 $0.00002 $0.00046

Measured 3d ago against content hash 9410a03e1747, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 3d 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.

commands/setup.md · 31 lines

What it actually says

Help the user enable the Slime HUD. Claude Code only. Never edit settings.json by hand — the script below does it safely (stable path, original saved, Windows-safe quoting).

  1. Show the current state (verbatim, it is already in the user's language):

    node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-statusline.js"

  2. Decide with the user:

    • No statusline yet → run replace (nothing to lose).
    • They already have their own statusline → recommend combine: their line stays exactly as it is (same command, same colours) and the Slime HUD is added as a row below it. Alternatives: replace (Slime only; theirs is saved), skip (leave everything, stop the reminder).
    • Slime is already installed → nothing to do; offer restore if they want their original statusline back.

  3. Apply the choice and show the output:

    node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-statusline.js" <combine|replace|skip|restore>

  4. The statusline refreshes by itself within a few seconds (Claude Code re-runs a changed statusLine command immediately); if it does not, restart Claude Code. Avoid suggesting /statusline — it regenerates the statusLine config and would overwrite Slime's.

Notes:

  • settings.json points at ~/.claude/slime/bin/statusline.js, a tiny shim that finds the current Slime version on every run — plugin updates can no longer leave a blank or broken statusline, and if Slime is uninstalled or disabled the shim shows the user's original statusline.
  • The user's original statusLine is saved in ~/.claude/slime/config.json → statusline.original; restore puts it back.
  • The session-start hook auto-installs the HUD only when no statusline exists (opt out: "autoHud": false in ~/.claude/slime/config.json).
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. 3d ago Changed · +8 lines · +16 tokens per session scan B → A 9410a03e1747
  2. 1mo ago First seen · 23 lines · 7 tokens per session scan B 4138fd765d8d

Subscribe to this mod's changes

setup is a command published in the GitHub repository bitqs/Slime (1 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 464 once invoked, about $0.0001 per session on Opus 5.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.

Claude Codeclaude-code-plugingamificationhookspixijsrpg
Related

Other commands, from other repositories

lint-config

Show or edit AgentLint configuration.

mauhpr/agentlint-plugin · 9 tokens

lint-status

Show AgentLint status — coverage, effective policy, session activity.

mauhpr/agentlint-plugin · 15 tokens

edit

An interview-style command for editing the trigger words used by existing personas. Personas are predefined viewpoints, such as a developer, designer, or lawyer, that guide how work is approached.

sodam-ai/SoDam-Persona · 44 tokens

fable-eval

Run the fable-mode eval suite (probes → pairwise judge → report). Costs tokens — runs headless claude many times. Optional arg: a probe id substring to filter.

rennf93/opus-fable-playbook · 38 tokens

decree

Issue a decree. Seats the organization on first use, then dispatches the teams.

MohamedEmbarak/Supreme-Leader · 17 tokens

report

The full account of the current decree — every figure verified before stated.

MohamedEmbarak/Supreme-Leader · 14 tokens