Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add kubalajiri/claude-squirrel/plugin install 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-config)<a href="https://agentmods.dev/commands/kubalajiri/claude-squirrel/squirrel-config"><img src="https://agentmods.dev/badge/commands/kubalajiri/claude-squirrel/squirrel-config/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kubalajiri/claude-squirrel/squirrel-config"><img src="https://agentmods.dev/badge/commands/kubalajiri/claude-squirrel/squirrel-config.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00023 | $0.00438 |
| Opus 5 | $0.00012 | $0.00219 |
| Sonnet 5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
squirrel-config 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 8d 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" --config "$ARGUMENTS"
Configuration resolves in three layers, the last one that sets a value winning:
| Layer | Where | What it is for |
|---|---|---|
| shipped | the plugin's own defaults/config.json |
the defaults, read-only |
| shared | ~/.squirrel/config.json |
settings you want in every profile |
| this profile | $CLAUDE_CONFIG_DIR/squirrel/config.json |
settings for this profile only |
With no arguments this lists every setting you have made and the layer it came from. That is the answer to "why is this not what I set?" — a value set in the shared layer and overridden here is reported as shadowing shared.
share copies this profile's settings down into the shared layer, so your other profiles pick
them up. It leaves this profile's own config exactly as it was, so running it here cannot
change anything you are looking at — it is safe to run and safe not to. It reports every
setting and what happened to it. Settings the shared layer already has are left alone rather
than overwritten, because those belong to your other profiles too.
Where an edit goes. Every editing command writes to the shared layer by default, unless
the setting is already set in this profile — in which case it keeps being edited here, so
nothing you have already configured moves under you. Add --here to any editing command to
write to this profile deliberately. Every command says which layer it wrote to.
A reset clears the setting from both layers, so it genuinely stops being set. Use
--here on a reset to clear only this profile and leave the shared value standing.
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.
- 8d ago First seen · 37 lines · 23 tokens per session scan A 0fedbd45f6cf
squirrel-config is a command published in the GitHub repository kubalajiri/claude-squirrel (2 stars, last pushed 14d ago), licensed MIT. It adds 23 tokens to every session and 438 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
hush
Silence all current and queued speech.
off
Disable narrator voice output.
buddy
Manage BuddyBar pet status, statusline, mode, evolution, prestige, and self-check.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
release
Generate changelog, bump version, and create git tag.