What is claude-code-env AGENTS.md?

Repository instructions for a small Go command-line program, including its file layout, build and test commands, and coding conventions.

They help with building, testing, formatting, linting, benchmarking, organizing files, naming code, and following the project’s configuration and backup practices.

They give an AI assistant the project-specific rules needed to make changes that fit the repository.

claude-code-env AGENTS.md — Instructions file by cexll

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 instructions/cexll/claude-code-env/agents-md

Clone the repo

git clone --depth 1 https://github.com/cexll/claude-code-env

Made for: Codex, OpenCode.

Per session 580 This file is loaded in full into every session.

When invoked 580 The same file — it is already loaded in full.

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.

Model	Per session	Once invoked
Fable 5	$0.00580	$0.00580
Opus 5	$0.00290	$0.00290
Sonnet 5	$0.00116	$0.00116
Haiku 4.5	$0.00058	$0.00058

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

Security

Grade A, and why

claude-code-env AGENTS.md 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.

AGENTS.md · 42 lines

How it starts

The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Repository Guidelines

This guide helps contributors work effectively on the simplified-cce Go CLI.

Project Structure & Module Organization

Module: simplified-cce; CLI entry at main.go.
Core files in repo root: launcher.go, config.go, ui.go.
Tests colocated as *_test.go (e.g., main_test.go).
CI workflows and templates in .github/; lint config in .golangci.yml.
Runtime config: ~/.claude-code-env/config.json; timestamped backups in ~/.claude-code-env/backups/.

Build, Test, and Development Commands

make build: Compile the CLI to ./cce.
make test: Run all unit tests verbosely.
make test-coverage: Generate coverage.out and coverage.html.
make bench: Execute benchmarks.
make fmt / make vet: Format imports/code and run vet checks.
golangci-lint run: Full lint suite per .golangci.yml.
Example subset: go test -run TestName ./....

Coding Style & Naming Conventions

Formatting: gofmt/goimports (run make fmt before committing).
Imports: group stdlib, third‑party, then local (simplified-cce/...).
Naming: Exported CamelCase; unexported camelCase.
Keep functions small; prefer table‑driven tests; avoid naked returns in long funcs.

Testing Guidelines

Framework: Go testing package; place tests next to sources as *_test.go.
Names: TestXxx for tests; BenchmarkXxx for benchmarks.
Coverage: maintain or improve; verify with make test-coverage.
Security: run make test-security for security‑focused tests when applicable.

Commit & Pull Request Guidelines

Commits: concise prefixes (feat:, fix:, chore:, docs:, refactor:, test:, style:); explain the "why" when non‑obvious.
PRs: clear description, linked issues (e.g., Closes #123), tests for changes, and CLI output/screenshots if behavior changes.
Quality gate: ensure make quality (and linters) pass before review.

Security & Configuration Tips

Do not commit secrets. Config lives under ~/.claude-code-env/ with 0700/0600 permissions; backups are created before edits (see config.go).
For code touching I/O or crypto, run gosec via golangci-lint locally.

Read the full file on GitHub · 42 lines

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.

2d ago First seen · 42 lines · 580 tokens per session scan A 8b7f1b380ed9

Subscribe to this mod's changes

claude-code-env AGENTS.md is an instructions file published in the GitHub repository cexll/claude-code-env (41 stars, last pushed 8mo ago), licensed MIT. It adds 580 tokens to every session, about $0.0029 per session on Opus 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.

Languages Testing

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.

openai/codex · 5,182 tokens

buildNext

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).

microsoft/vscode · 6,785 tokens

claude-code-env AGENTS.md