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/prestigegit 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.00016 | $0.00177 |
| Opus 5 | $0.00008 | $0.00088 |
| Sonnet 5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
prestige 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.
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
Help the user prestige (New Game+). This resets level and XP, so always confirm first.
-
Run the dry-run and show its output verbatim:
node "${CLAUDE_PLUGIN_ROOT}/scripts/prestige.js" -
If it says "not yet", stop — they haven't reached the level requirement.
-
If it says "ready", make sure the user clearly understands their level and XP will be reset to 0 (badges, streak and milestones are kept) and explicitly confirms. Only after a clear yes:
node "${CLAUDE_PLUGIN_ROOT}/scripts/prestige.js" --yes -
Show the result.
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 · 24 lines · 16 tokens per session scan A 747936e3fd8c
prestige is a command published in the GitHub repository bitqs/Slime (1 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 177 once invoked, about $0.0001 per session on Opus 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.
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.