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/texmeijin/claude-code-mascot-statusline/setupgit clone --depth 1 https://github.com/TeXmeijin/claude-code-mascot-statuslineWrote 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/texmeijin/claude-code-mascot-statusline/setup)<a href="https://agentmods.dev/commands/texmeijin/claude-code-mascot-statusline/setup"><img src="https://agentmods.dev/badge/commands/texmeijin/claude-code-mascot-statusline/setup.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.00013 | $0.01730 |
| Opus 5 | $0.00006 | $0.00865 |
| Sonnet 5 | $0.00003 | $0.00346 |
| Haiku 4.5 | $0.00001 | $0.00173 |
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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 0: Choose mascot pack
Ask the user which mascot pack they want to use.
Use AskUserQuestion (adapt language to the user's language):
- Question: Which mascot pack would you like to use?
- Options:
- "pixel-buddy" — A pixel-art cat that reacts to your coding session (default)
- "space-invader" — A retro arcade-style space invader
If the user chooses pixel-buddy, skip to Step 1 (it's the default, no config needed).
If the user chooses space-invader, proceed to Step 0.5.
Step 0.5: Choose scope (space-invader only)
Ask the user where they want to apply the space-invader pack.
The config directory is $CLAUDE_CONFIG_DIR if set, otherwise ~/.claude. Resolve it first:
echo "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
Use AskUserQuestion (adapt language to the user's language):
- Question: Where should the space-invader pack be applied?
- Options:
- "All projects (user global)" — Writes to
<config-dir>/plugins/claude-code-mascot-statusline/config.json - "This project only" — Writes to
.claude/mascot.jsonin the current project
- "All projects (user global)" — Writes to
Based on the user's choice, write the config file:
For user global:
mkdir -p "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/plugins/claude-code-mascot-statusline"
Then use the Write tool to write <resolved-config-dir>/plugins/claude-code-mascot-statusline/config.json:
{
"pack": "space-invader"
}
For this project only:
mkdir -p .claude
Then use the Write tool to write .claude/mascot.json:
{
"pack": "space-invader"
}
Confirm to the user which path was written.
Step 0.7: Customize summary items (optional)
Ask the user if they want to customize which items appear in the status line summary.
Use AskUserQuestion (adapt language to the user's language):
- Question: Would you like to customize the status line summary items?
- Options:
- "Show all (default)" — Show all available items
- "Customize" — Choose which items to display
If the user chooses Show all, skip to Step 1.
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.
- 5d ago First seen · 201 lines · 13 tokens per session scan A c4c2a631b355
setup is a command published in the GitHub repository TeXmeijin/claude-code-mascot-statusline (24 stars, last pushed 4mo ago), licensed MIT. It adds 13 tokens to every session and 1,730 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-30.
Other commands, from other repositories
setup
Install & set up newsline — rotating regional news in your status line (keeps your existing status line).
setup
Configure the statusline in Claude Code settings.
cleanup
Remove statusline configuration before uninstalling the plugin.
configure
Adjust what ClaudeMeter shows in your statusline.
setup
Configure ClaudeMeter as your Claude Code statusline.
tmux-squad
Open a grid of panes for watching several agents at once — one primary plus N workers.