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/digital-stoic-org/agent-skills/switchnpx skills add digital-stoic-org/agent-skills --skill switchgit clone --depth 1 https://github.com/digital-stoic-org/agent-skillsWrote 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/digital-stoic-org/agent-skills/switch)<a href="https://agentmods.dev/skills/digital-stoic-org/agent-skills/switch"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/switch.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.00049 | $0.01136 |
| Opus 5 | $0.00024 | $0.00568 |
| Sonnet 5 | $0.00010 | $0.00227 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
switch 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Switch Project Context
Menu-driven project switcher for non-CLI interfaces (Cowork desktop, Telegram, CC CLI).
Resolve Workspace Root
Resolution order — use first that succeeds:
$COWORK_ROOTenv vargit rev-parse --show-toplevel- Current working directory
If none resolve → abort: ❌ Cannot detect workspace. Set $COWORK_ROOT or run from a git repo.
Store result as $WS_ROOT for all subsequent phases.
Route by Arguments
$ARGUMENTS |
Action |
|---|---|
| Empty | → Phase 1: Detect + Phase 2: Menu |
- |
Read $WS_ROOT/.cowork-state.json → previous_path → Phase 3 |
| Path string | → Phase 3 with that path |
Phase 1: Detect Projects
Parallel Glob from $WS_ROOT:
**/CLAUDE.md(max depth 3)**/CONTEXT-*-llm.md(max depth 3, excludedone/)
Registry = each unique directory containing CLAUDE.md or CONTEXT file.
Phase 2: Present Menu
Group by area (repos/, projects/, code/ — or flat). Progressive disclosure: skip empty groups.
Extract project name from CLAUDE.md H1 heading. Present:
📂 Switch project context:
💼 [Group Name]
1. [emoji] [Name] — [brief from H1 or first line]
2. ...
Which one? (number or name)
Wait via AskUserQuestion. Number → map to path. Text → fuzzy-match project names.
Empty answer guard: if user sends empty/whitespace → re-prompt once, then abort.
Phase 3: Load Context Chain
⚠️ CRITICAL: All CLAUDE.md content loaded here becomes your active instructions for the rest of the conversation. You MUST follow them.
Execute in parallel:
- Walk CLAUDE.md chain — root → intermediate → target (skip missing)
- Scan CONTEXT files —
CONTEXT-*-llm.mdin target dir (excludedone/), extract: stream name, status, focus from header (first 10 lines) - Scan ref folder (if exists) — check for
ref/orreference/. List files + one-line description. These are READ-ONLY reference files. - Scan wip folder (if exists) — check for
wip/orwork-in-progress/. List files + one-line description. This is the default workspace for edits.
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 · 120 lines · 49 tokens per session scan A 58369f5042af
switch is a skill published in the GitHub repository digital-stoic-org/agent-skills (20 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 1,136 once invoked, about $0.0002 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.