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 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/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/skills/digital-stoic-org/agent-skills/switch"><img src="https://agentmods.dev/badge/skills/digital-stoic-org/agent-skills/switch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 5 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.5 | $0.00020 | $0.00454 |
| Sonnet 5.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 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 — 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.
- 1mo 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 12d ago), licensed MIT. It adds 49 tokens to every session and 1,136 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…