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/squirrel-plannpx skills add thgMatajs/squirrel-mode --skill squirrel-plangit 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/skills/thgmatajs/squirrel-mode/squirrel-plan)<a href="https://agentmods.dev/skills/thgmatajs/squirrel-mode/squirrel-plan"><img src="https://agentmods.dev/badge/skills/thgmatajs/squirrel-mode/squirrel-plan.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.00096 | $0.01312 |
| Opus 5 | $0.00048 | $0.00656 |
| Sonnet 5 | $0.00019 | $0.00262 |
| Haiku 4.5 | $0.00010 | $0.00131 |
Grade A, and why
squirrel-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 3d 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.
This is a copy
94% identical to plan — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
squirrel-mode plan (Cursor)
This skill 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.
- 3d ago First seen · 78 lines · 96 tokens per session scan A 950eb086dcde
squirrel-plan is a skill published in the GitHub repository thgMatajs/squirrel-mode (2 stars, last pushed 15d ago), licensed MIT. It adds 96 tokens to every session and 1,312 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to plan, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
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.
glossary-init
USE WHEN setting up a repo for AI-first work, when an agent hallucinates domain term meaning, or when user asks to bootstrap / extend the repo's domain glossary. Surfaces candidate terms by identifier frequency, asks the user for 1-sentence definitions, writes GLOSSARY.md at repo root. Idempotent — re-running adds new…
codex-pair-resume
Resume codex-pair for this project after a previous pause. Removes .codex-pair/state/paused and clears failure state. Review resumes on the next supported file edit; missing state is a no-op.
conventions-init
USE WHEN setting up a repo for AI-first work (after /init-repo), or when the context-surface hook should start feeding repo conventions to agents before edits. Drafts conventions.yml at repo root: per-kind casing (inferred from the code), a vague-name denylist seed, directory roles, and a hand-filled house-rules…
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
codex-review
Get a second opinion from OpenAI Codex on your current code changes. Analyzes staged/unstaged diffs and returns prioritized findings. Use when user asks to "review with Codex", "Codex code review", or "ask Codex to check my code".