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/team-attention/mcproxy/claude-mdgit clone --depth 1 https://github.com/team-attention/mcproxyWhat 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.00384 | $0.00384 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
mcproxy 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 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
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
MCP Proxy for Claude Code - intercepts MCP server requests and filters tools based on .mcproxy.json configuration. Allows users to enable/disable specific MCP tools to reduce token consumption.
Commands
npm run build # Compile TypeScript to dist/
npm test # Run tests in watch mode
npm test -- --run # Run tests once
npm run dev # Run with tsx (development)
Architecture
Message Flow:
Claude Code ←→ mcproxy (stdio) ←→ MCP Server (subprocess)
↓
.mcproxy.json (tool config)
Key Modules:
src/index.ts- CLI entry point using Commandersrc/proxy/mcp-proxy.ts- Main proxy class, manages upstream subprocess and stdio streamssrc/proxy/message-handler.ts- Interceptstools/list(filters response) andtools/call(blocks disabled tools)src/config/config-manager.ts- Manages.mcproxy.jsonfile, auto-registers new tools withenabled: truesrc/config/mcp-config-reader.ts- Reads.mcp.jsonto auto-detect server name for config keyssrc/filter/tool-filter.ts- Simple filter logic using ConfigManager
Server Name Resolution:
The proxy reads .mcp.json to find which server name (e.g., "linear", "github") matches the current upstream command, then uses that as the key in .mcproxy.json.
File Naming
Use kebab-case for all TypeScript files (e.g., mcp-proxy.ts, config-manager.ts).
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 · 41 lines · 384 tokens per session scan A 7f09b45990d7
mcproxy CLAUDE.md is an instructions file published in the GitHub repository team-attention/mcproxy (20 stars, last pushed 7mo ago), licensed MIT. It adds 384 tokens to every session, about $0.0019 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.
Other instructions, from other repositories
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).
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.
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.