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 commands/bitqs/slime/setupgit clone --depth 1 https://github.com/bitqs/SlimeWhat 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.00007 | $0.00283 |
| Opus 5 | $0.00003 | $0.00142 |
| Sonnet 5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade B, and why
setup scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
2. Read `~/.claude/settings.json`. If a `statusLine` key exists, show it and ask before replacing. What it actually says
Help the user enable the Slime HUD:
Claude Code only.
- Resolve the plugin root: the directory containing this command file, up one level.
- Read
~/.claude/settings.json. If astatusLinekey exists, show it and ask before replacing. - Set:
{ "statusLine": { "type": "command", "command": "node \"<PLUGIN_ROOT>/scripts/statusline.js\"", "refreshInterval": 2 } }
(refreshInterval: 2 re-runs the HUD every 2s on top of event updates, so the ⏱ session clock ticks live instead of only on tool calls. If a statusLine already exists, preserve any refreshInterval the user set.)
- Tell the user to restart Claude Code to see the HUD. (Avoid suggesting
/statusline— that command regenerates the statusLine config and would overwrite Slime's.)
Note: for most users this is optional — Slime's session-start hook auto-installs the statusLine on first run (unless ~/.claude/slime/config.json has "autoHud": false, or a statusLine is already set). /slime:setup is the manual fallback.
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.
- yesterday First seen · 23 lines · 7 tokens per session scan B 4138fd765d8d
setup is a command published in the GitHub repository bitqs/Slime (1 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 283 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
VibeGuard: ExecPlan
Long-term task execution plan — generates self-contained execution documents from SPEC, supports cross-session recovery.
VibeGuard: Review
Structured code review - first run the guard to obtain the baseline, then review according to security → logic → quality → performance priority.
VibeGuard: Live Truth
Verify live claims with fresh facts, inferences, and unresolved gaps.
VibeGuard: Stats
View hooks trigger statistics - interception/warning/release times and reason analysis.
safe-build
Build the application for development or production.
memory
Use when: user asks to remember something, after solving a non-obvious problem, or to capture key session findings.