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-layout)<a href="https://agentmods.dev/commands/kubalajiri/claude-squirrel/squirrel-layout"><img src="https://agentmods.dev/badge/commands/kubalajiri/claude-squirrel/squirrel-layout.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.1 | $0.00027 | $0.00482 |
| Opus 5 | $0.00014 | $0.00241 |
| Sonnet 5 | $0.00005 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
squirrel-layout 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 6d 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" --layout "$ARGUMENTS"
With no arguments this prints the layout line by line, each segment followed by its drop
priority — the rank that decides what survives when the pane gets narrow, higher surviving
longer, always never dropped — plus protected for the two segments that can never be
removed (account, model), off for a segment hidden with /squirrel-show, and the list
of registered segments that are not placed on any line.
Lines and positions are numbered from 1. The layout can have any number of lines: one, two (the shipped arrangement), four — Claude Code prints whatever the status line emits.
move <segment> <line> [position]— move one segment; a line number one past the end creates a new line, and an omitted position appends to the end of that line.line <n> <segment> <segment> ...— set one whole line at once; the named segments are removed from wherever else they were.swap <a> <b>— exchange two whole lines.priority <segment> <n|always>— how hard that segment clings to a narrow pane.reset— restore the shipped layout and discard every priority override.
Every edit is surgical: it rewrites only the layout, never the rest of the user's config, and
is validated before anything is written. An unknown segment id, a line number out of range, or
an edit that would leave account or model unplaced is refused with a message and nothing
is written. Never construct or write the layout / segmentPriority config keys by hand —
always go through this command.
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.
- 6d ago First seen · 34 lines · 0 tokens per session scan A e9d17dec481e
squirrel-layout is a command published in the GitHub repository kubalajiri/claude-squirrel (2 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 482 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
anti-slop-designer
Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.
design-enforce
Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.
design-grill
Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.
design-triage
Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.
audit
Run a full UI/UX design audit on the current project. Scores 12 dimensions and produces a markdown report with prioritized findings.
design-brief
Use when a design request is broad or unclear and you do not know which specialist it needs. Reads the brief, routes it to the right expertise, and returns structured guidance.