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 commands/runnithan/claudex-setup/environment-switching-local-cloud-sshgit clone --depth 1 https://github.com/runnithan/claudex-setupWrote 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/commands/runnithan/claudex-setup/environment-switching-local-cloud-ssh)<a href="https://agentmods.dev/commands/runnithan/claudex-setup/environment-switching-local-cloud-ssh"><img src="https://agentmods.dev/badge/commands/runnithan/claudex-setup/environment-switching-local-cloud-ssh.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.00000 | $0.00288 |
| Opus 5 | $0.00000 | $0.00144 |
| Sonnet 5 | $0.00000 | $0.00058 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
environment-switching-local-cloud-ssh 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 4d 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.
What it actually says
Switch Execution Environment (Local / Cloud / SSH) to Match the Workload
TL;DR
The environment selector at the bottom of Claude Code switches where work executes: local for fast interactive iteration, cloud (Anthropic servers) for routines that must run with your machine off, SSH for driving a remote box like a VPS.
Why it matters
People default to local for everything and then wonder why scheduled work dies when the laptop sleeps. The execution environment is a one-click choice per task: interactive dev wants local speed; unattended automation wants cloud persistence; workloads needing your own infra (GPUs, private network, persistent disk) want SSH.
How to apply
Click the environment indicator (shows "local") at the bottom of the Claude Code window and pick cloud or SSH. Rule of thumb: local for anything you're watching; cloud for routines/scheduled agents; SSH when the job must run on a specific remote machine. Pairs with vps-tmux-telegram-persistent-sessions for the self-hosted variant.
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.
- 4d ago First seen · 24 lines · 0 tokens per session scan A 9bf5a8f9f63b
environment-switching-local-cloud-ssh is a command published in the GitHub repository runnithan/claudex-setup (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 288 tokens. 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 commands, from other repositories
cloudflare-images:validate-config
Validate wrangler.jsonc configuration, verify Cloudflare Images bindings, check environment variables, and test Workers integration. Ensures correct setup for using Cloudflare Images with Cloudflare Workers.
cloudflare-queues:setup
Interactive wizard to set up Cloudflare Queues with queue creation, producer/consumer binding configuration, and Dead Letter Queue setup. Use when user wants to create first queue or add queues to existing Worker.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.
cloudflare-images:check
Run comprehensive health check and configuration validation for Cloudflare Images. Tests API connectivity, verifies authentication, checks transformations enabled, lists variants, and shows quota usage.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.