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/onnpx skills add thgMatajs/squirrel-mode --skill ongit 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/on)<a href="https://agentmods.dev/skills/thgmatajs/squirrel-mode/on"><img src="https://agentmods.dev/badge/skills/thgmatajs/squirrel-mode/on.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.00028 | $0.01153 |
| Opus 5 | $0.00014 | $0.00576 |
| Sonnet 5 | $0.00006 | $0.00231 |
| Haiku 4.5 | $0.00003 | $0.00115 |
Grade A, and why
on 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
squirrel-mode on
/squirrel:on reverses /squirrel:off for the current session. It is a no-op, confirmed the same way, if the session was never turned off.
Why this cannot flip a flag directly (ADR-0005)
Exactly the same problem /squirrel:off has: this skill has no way to learn this session's own session id, so it cannot name the one file it would need to remove. It leaves a note for the UserPromptSubmit hook - which does see the real session id on the next prompt - and lets that hook clear the flag.
Find the session off-token and working directory first
Your context already contains two lines, injected at the start of this session:
Session off-token: <token>- the opaque token this skill embeds in the sentinel filename. Copy that exact string. Do not invent a token, do not shorten it, do not substitute a random suffix of your own: theUserPromptSubmithook recomputes the same value from the session id it receives on stdin, and a token you invent is one it cannot match.Session working directory: <value>- the exact value written into the sentinel's contents (legacy dual-match / cwd path). Never determine this yourself by running a command, inspecting your own state, or any other means: a value you determine yourself can disagree with the one the claiming hook compares against on the legacy path (a symlinked project path, a trailing slash, a different shell context), and the mismatch is silent.
If the off-token line is missing entirely, or present but empty after the colon, tell the user in one line that the session off-token cannot be determined and stop. Do not write a sentinel in that case.
If the token begins with anon-, tell the user in one line that this session cannot be turned back on - for example: "This session cannot be turned back on: squirrel-mode was not given a session id for it. A new session restores /squirrel:on." - and stop. Do not write a sentinel in that case either. An anon- token is what squirrel-mode emits when this session's id was missing or unusable, and it is documentation only: the UserPromptSubmit hook that claims sentinels recomputes the token from that same session id, so it can never arrive at an anon- one. A CLEAR.anon-... file would sit there unclaimed for the whole session while the user had been told the change was coming. Such a session cannot have been turned off by /squirrel:off either, for exactly the same reason, so there is nothing to reverse.
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 · 43 lines · 28 tokens per session scan A 3b8db64202b8
on is a skill published in the GitHub repository thgMatajs/squirrel-mode (2 stars, last pushed 15d ago), licensed MIT. It adds 28 tokens to every session and 1,153 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 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".