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.
git clone --depth 1 https://github.com/thgMatajs/squirrel-modeWrote 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/thgmatajs/squirrel-mode/plan)<a href="https://agentmods.dev/commands/thgmatajs/squirrel-mode/plan"><img src="https://agentmods.dev/badge/commands/thgmatajs/squirrel-mode/plan/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/thgmatajs/squirrel-mode/plan"><img src="https://agentmods.dev/badge/commands/thgmatajs/squirrel-mode/plan.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.00000 | $0.01202 |
| Opus 5.5 | $0.00000 | $0.00481 |
| Sonnet 5.5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
plan 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
squirrel-mode plan (Cursor)
This command turns a raw, disordered idea into a scoped, startable plan. Divergent thinking is not the hard part here; convergence, getting started, and not losing the tangents are. This command converges, hands back one startable action, and captures tangents instead of dropping them.
Step 1: get the idea
If nothing was provided with the request and nothing else was pasted, ask exactly one question: "Tell me the idea - messy is fine." Then stop and wait for the reply. Otherwise, treat whatever was provided, plus anything pasted with it, as the idea dump, in whatever state of disorder it arrives in.
Step 2: clarify, at most 3 questions
Ask at most 3 clarifying questions, one at a time, waiting for each reply before asking the next. Make each question multiple-choice whenever the possible answers are enumerable. Never ask an open-ended "tell me more" question. Skip any question whose answer is already inferable from the dump: 3 is a ceiling, not a target, and 0 clarifying questions is a valid outcome when the dump is clear enough.
This ceiling of 3 covers every clarifying question this command ever asks, including Step 3's own "ask the user to pick" fallback below - that fallback is not a bonus round after this cap, it draws from the same budget. Track how many of the 3 you have already spent before reaching Step 3.
If the dump describes a genuine fork in approach (for example: a CLI tool or a web app), present that fork as one multiple-choice clarifying question before writing the plan. Never write two parallel plans for the two branches of a fork.
Step 3: converge and write the plan
Do not keep iterating once Step 2 is done. Produce the plan below in one pass.
Write the plan in the profile's language field. If there is no profile, or language is auto, mirror the language the user is currently writing in.
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.
- 1mo ago First seen · 72 lines · 0 tokens per session scan A e061f188ba38
plan is a command published in the GitHub repository thgMatajs/squirrel-mode (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,202 tokens. 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
evaluate
You are running the evaluation phase of the current Grainulator sprint. This is the honesty phase — where claims meet data.
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
setup
Get started with ClawdBod — set your break cadence and an optional profile for calorie estimates.