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 skills/thgmatajs/squirrel-mode/plannpx skills add thgMatajs/squirrel-mode --skill plangit clone --depth 1 https://github.com/thgMatajs/squirrel-modeWhat 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.00102 | $0.01279 |
| Opus 5 | $0.00051 | $0.00639 |
| Sonnet 5 | $0.00020 | $0.00256 |
| Haiku 4.5 | $0.00010 | $0.00128 |
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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- squirrel-plan — 94% identical, 13 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
squirrel-mode plan
Arguments: $ARGUMENTS
/squirrel:plan 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 $ARGUMENTS is empty and nothing else was provided, ask exactly one question: "Tell me the idea - messy is fine." Then stop and wait for the reply. Otherwise, treat $ARGUMENTS, 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.
Use exactly this section structure, in this order:
## The idea in one sentence
<forces convergence>
## Goal
<what success looks like, concretely, 1-2 lines>
## Scope
- IN: <3-5 bullets max>
- OUT (for now): <explicitly deferred - a decision, not a loss>
## Smallest useful version
<the minimal version that already delivers value - days, not months>
## Plan
Phase 1 - <name> (expanded fully below, in the form set by `step_style`, respecting max_list_items)
Phase 2 - <name> (one-line summary only)
Phase 3 - <name> (one-line summary only)
## First action
<ONE step, startable in under 10 minutes, right now>
## Parking lot 🐿️
<every tangent and "what if" that came up - captured, but explicitly not in the plan>
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.
- 2d ago First seen · 75 lines · 102 tokens per session scan A 088185cace74
plan is a skill published in the GitHub repository thgMatajs/squirrel-mode (2 stars, last pushed 14d ago), licensed MIT. It adds 102 tokens to every session and 1,279 once invoked, about $0.0005 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 skills, from other repositories
adhd-and-47-tabs
Use when a user needs a direct, low-friction response for research, studying, writing, planning, decisions, administrative work, troubleshooting, or a multi-turn project, especially when they seem overwhelmed, distracted, stuck starting, interrupted, burdened by too many options, or likely to lose the active thread.
hyperfocus
ADHD-friendly output formatting. Restructures responses with chunking, visual hierarchy, and front-loaded key points. Modes: clean, flow (default), zen. Use when user says "hyperfocus", "focus mode", "adhd mode", "adhd friendly", or invokes /hyperfocus.
task-anchor
Version: 1.0 Activation: MANDATORY on every session start Persona: Executive Function Proxy (firm, non-judgmental, binary choices only).
git-rollback
Interactively rollback Git branch to historical version; lists branches, versions, then executes reset/revert after confirmation.
golden-rss
Use when testing the rss golden build.
design-system-builder
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.