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/idonisso/claude-code-palate-cleanser/playgit clone --depth 1 https://github.com/IdoNisso/claude-code-palate-cleanserWrote 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/commands/idonisso/claude-code-palate-cleanser/play)<a href="https://agentmods.dev/commands/idonisso/claude-code-palate-cleanser/play"><img src="https://agentmods.dev/badge/commands/idonisso/claude-code-palate-cleanser/play.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00011 | $0.00149 |
| Opus 5 | $0.00005 | $0.00075 |
| Sonnet 5 | $0.00002 | $0.00030 |
| Haiku 4.5 | $0.00001 | $0.00015 |
Grade A, and why
play 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 4d 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
Launch the palate cleanser typing game in a new terminal tab/window so the user can play while waiting.
Use the Bash tool to detect the terminal emulator and open the game accordingly.
IMPORTANT: Copy the script below EXACTLY as written. Do not paraphrase, summarize, or rewrite any part of it.
bash "${CLAUDE_PLUGIN_ROOT}/commands/scripts/launch-game.sh"
After launching, tell the user:
- The game is running in the other terminal
- When Claude finishes a task, they'll hear a bell and see a "Claude is ready!" notification in the game
- They can quit with Ctrl+Q
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.
- 4d ago First seen · 19 lines · 11 tokens per session scan A cfc724425753
play is a command published in the GitHub repository IdoNisso/claude-code-palate-cleanser (3 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 149 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
setup
Install & set up newsline — rotating regional news in your status line (keeps your existing status line).
tmux-squad
Open a grid of panes for watching several agents at once — one primary plus N workers.
tmux-project
Open (or reuse) a project workspace session — server / agent / editor.
tmux-status
Show every live tmux session, pane, and exit code, with attach commands.
setup
Configure claude-code-mascot-statusline statusLine and hooks.
uninstall
Remove claude-code-mascot-statusline statusLine, hooks, and runtime data.