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/1shooperman/claude-env/activategit clone --depth 1 https://github.com/1shooperman/claude-envWhat 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.00240 |
| Opus 5 | $0.00000 | $0.00120 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
activate 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.
What it actually says
claudenv <name>
Activate a named env.
Usage
claudenv work
claudenv personal
claudenv default # maps to ~/.claude (your original config)
What it does
Sets CLAUDE_CONFIG_DIR to ~/.claudenv/envs/<name>/ so Claude Code reads config and credentials from that directory. Updates your shell prompt to show the active env name.
If another env is already active, it is silently deactivated first.
The default env
claudenv default is a built-in reserved name that maps CLAUDE_CONFIG_DIR to ~/.claude — your original Claude Code home. It lets you switch back to your primary account without fully deactivating.
Errors
| Message | Cause |
|---|---|
claudenv: no such env "…" |
The named env directory does not exist — run claudenv list or claudenv config to create it |
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.
- 2d ago First seen · 35 lines · 0 tokens per session scan A ecbe3bb366c6
activate 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 240 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
team
Route a task to the right AI team + member (two-level team→member selection).
sync
Stage, commit, and push pending changes via the gss skill in one guided flow.
gss-pr
Create a feature branch and open a pull request via gss pr.
ssh-find
Find an SSH host on the local network and update /.ssh/config with its current IP.
ssh-keys
Manage SSH keys across hosts — generate, sync, list status, or delete.
tmux-agent
Orchestrate parallel agents via tmux-mgr (start / list / complete / cleanup).