index

A shell-based tool for creating and switching between separate Claude Code environments. An environment is an isolated setup with its own configuration and credentials.

In plain words
What is it for?
Use it to choose, activate, deactivate, list, configure, upgrade, remove, or get help for Claude Code environments.
Why use it?
It keeps different projects or configurations separate, so changing one environment does not require manually rebuilding another.

Command

Install

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.

agentmods
npx agentmods add commands/1shooperman/claude-env/index
Clone the repo
git clone --depth 1 https://github.com/1shooperman/claude-env
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 195 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00195
Opus 5 $0.00000 $0.00097
Sonnet 5 $0.00000 $0.00039
Haiku 4.5 $0.00000 $0.00019

Measured 2d ago against content hash d94b268aa318, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

index 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 2d 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.

docs/commands/index.md · 23 lines

What it actually says

Commands

All claudenv commands are subcommands of the claudenv shell function.

Command Description
claudenv Interactive env picker
claudenv <name> Activate a named env
claudenv deactivate Deactivate the current env
claudenv config Create a new env
claudenv list List all envs
claudenv remove Delete an env
claudenv upgrade Upgrade claudenv to a release
claudenv uninstall Remove claudenv
claudenv help Show command reference
Changes

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.

  1. 2d ago First seen · 23 lines · 0 tokens per session scan A d94b268aa318

Subscribe to this mod's changes

index is a command published in the GitHub repository 1shooperman/claude-env (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 195 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.