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/kubalajiri/claude-squirrel/squirrel-setupgit clone --depth 1 https://github.com/kubalajiri/claude-squirrelWrote 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/kubalajiri/claude-squirrel/squirrel-setup)<a href="https://agentmods.dev/commands/kubalajiri/claude-squirrel/squirrel-setup"><img src="https://agentmods.dev/badge/commands/kubalajiri/claude-squirrel/squirrel-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.00011 | $0.00116 |
| Opus 5 | $0.00005 | $0.00058 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
squirrel-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.
What it actually says
Run this exact command with the Bash tool and show the user its output verbatim:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/squirrel.sh" --setup "${CLAUDE_PLUGIN_ROOT}"
Then tell the user, in at most three lines: the status line is active (it may take a moment to appear), the activity-state hooks are active because the plugin is installed, and they can label this account with /squirrel-nick <name>. Do not do anything else.
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 · 10 lines · 11 tokens per session scan A f2a21cda3cc5
squirrel-setup is a command published in the GitHub repository kubalajiri/claude-squirrel (2 stars, last pushed 10d ago), licensed MIT. It adds 11 tokens to every session and 116 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
status
Show claude-bionify's current settings.
set
Change a claude-bionify setting, e.g. "fixation 0.7" or "boundary syllable".
off
Turn claude-bionify off so Claude's replies render normally.
on
Turn claude-bionify on so Claude's replies are bolded.
reset
Clear all live claude-bionify overrides, back to your configured defaults.
toggle
Flip claude-bionify on or off.