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 instructions/cexll/claude-code-env/claude-mdgit clone --depth 1 https://github.com/cexll/claude-code-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.01772 | $0.01772 |
| Opus 5 | $0.00886 | $0.00886 |
| Sonnet 5 | $0.00354 | $0.00354 |
| Haiku 4.5 | $0.00177 | $0.00177 |
Grade B, and why
claude-code-env CLAUDE.md scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Fix: `chmod 700 ~/.claude-code-env/` How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
Claude Code Environment Switcher (CCE) is a lightweight Go CLI tool that manages multiple Claude Code API endpoint configurations, allowing seamless switching between different environments (production, staging, custom API providers, etc.). The tool acts as a wrapper around Claude Code, injecting appropriate environment variables before launching.
Commands
Build and Test
# Build binary
make build # or: go build -o cce .
# Run all tests
make test # or: go test -v ./...
# Run specific test
go test -v -run TestValidateName ./... # Run single test by name
go test -v -run "TestSecurity" ./... # Run all security tests
go test -v -run "TestFlagPassthrough" ./... # Run flag passthrough tests
# Test coverage
make test-coverage # Generate HTML coverage report
go test -coverprofile=coverage.out ./... # Generate coverage profile
# Performance benchmarks
make bench # or: go test -bench=. -benchmem ./...
# Code quality
make quality # Runs fmt + vet + test
make fmt # Format all Go files
make vet # Run static analysis
# Security tests
make test-security # or: go test -v -run TestSecurity ./...
# Clean build artifacts
make clean # Remove cce binary and coverage files
Installation
# Install to system PATH
make install # Builds and moves to /usr/local/bin/
# Development build
go build -o cce . # Build binary in current directory
Architecture
The project uses a minimalist 4-file architecture following KISS principles:
Core Components
main.go (580+ lines)
- CLI entry point and command routing
- Two-phase argument parser for flag passthrough system
- Model validation with configurable patterns
- Environment validation (name, URL, API key)
- Help text generation with flag passthrough examples
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 · 252 lines · 1,772 tokens per session scan B f63ed2573080
claude-code-env CLAUDE.md is an instructions file published in the GitHub repository cexll/claude-code-env (41 stars, last pushed 8mo ago), licensed MIT. It adds 1,772 tokens to every session, about $0.0089 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.