claude-code-proxy: Instructions file for Claude Code

CLAUDE.md

claude-code-proxy CLAUDE.md is an instructions file for Claude Code from fuergaosi233/claude-code-proxy. It costs 2,202 tokens per session, scanned A, original, MIT.

Collaboration instructions for working with Claude Code on software projects. They describe how to break down tasks, search files, read large files, and make edits reliably.

In plain words
What is it for?
Use them to plan complex tasks, keep a task list, find targeted code, choose how much of a file to read, and apply changes safely.
Why use it?
They make multi-step coding work easier to track and reduce mistakes caused by editing files without enough context or inserting code in the wrong place.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: names the TodoWrite tool; mentions Claude Code.

This is fuergaosi233/claude-code-proxy's own configuration. It tells Claude Code how to work on claude-code-proxy itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything claude-code-proxy configures →

About the project

Claude Code Proxy is a server that translates Claude Code API requests into calls to OpenAI-compatible model providers. It lets Claude Code users connect the CLI to services such as OpenAI, Azure OpenAI, Ollama, local models, or other compatible endpoints. The catalogue instruction helps configure or use this proxy.

fuergaosi233/claude-code-proxy · 2,785 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to fuergaosi233/claude-code-proxy. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/fuergaosi233/claude-code-proxy/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/fuergaosi233/claude-code-proxy

Made for: Claude Code.

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

agentmods badge for claude-code-proxy CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/fuergaosi233/claude-code-proxy/claude-md.svg)](https://agentmods.dev/instructions/fuergaosi233/claude-code-proxy/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/fuergaosi233/claude-code-proxy/claude-md"><img src="https://agentmods.dev/badge/instructions/fuergaosi233/claude-code-proxy/claude-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 2,202 This file is loaded in full into every session.
When invoked 2,202 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02202 $0.02202
Opus 5 $0.01101 $0.01101
Sonnet 5 $0.00440 $0.00440
Haiku 4.5 $0.00220 $0.00220

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

Security

Grade A, and why

claude-code-proxy CLAUDE.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 8d 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.

CLAUDE.md · 127 lines

How it starts

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

Claude Code: Best Practices for Effective Collaboration

This document outlines best practices for working with Claude Code to ensure efficient and successful software development tasks.

Task Management

For complex or multi-step tasks, Claude Code will use:

  • TodoWrite: To create a structured task list, breaking down the work into manageable steps. This provides clarity on the plan and allows for tracking progress.
  • TodoRead: To review the current list of tasks and their status, ensuring alignment and that all objectives are being addressed.

File Handling and Reading

Understanding file content is crucial before making modifications.

  1. Targeted Information Retrieval:

    • When searching for specific content, patterns, or definitions within a codebase, prefer using search tools like Grep or Task (with a focused search prompt). This is more efficient than reading entire files.
  2. Reading File Content:

    • Small to Medium Files: For files where full context is needed or that are not excessively large, the Read tool can be used to retrieve the entire content.
    • Large File Strategy:
      1. Assess Size: Before reading a potentially large file, its size should be determined (e.g., using ls -l via the Bash tool or by an initial Read with a small limit to observe if content is truncated).
      2. Chunked Reading: If a file is large (e.g., over a few thousand lines), it should be read in manageable chunks (e.g., 1000-2000 lines at a time) using the offset and limit parameters of the Read tool. This ensures all content can be processed without issues.
    • Always ensure that the file path provided to Read is absolute.

File Editing

Precision is key for successful file edits. The following strategies lead to reliable modifications:

  1. Pre-Edit Read: Always use the Read tool to fetch the content of the file immediately before attempting any Edit or MultiEdit operation. This ensures modifications are based on the absolute latest version of the file.

Read the full file on GitHub · 127 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.

  1. 8d ago First seen · 127 lines · 2,202 tokens per session scan A d5aa47d2d8ac

Subscribe to this mod's changes

claude-code-proxy CLAUDE.md is an instructions file published in the GitHub repository fuergaosi233/claude-code-proxy (2,785 stars, last pushed 6mo ago), licensed MIT. It adds 2,202 tokens to every session, about $0.0110 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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,153 tokens

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

microsoft/vscode · 6,785 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens