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/smart-mcp-proxy/mcpproxy-go/claude-mdgit clone --depth 1 https://github.com/smart-mcp-proxy/mcpproxy-goWhat 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.03515 | $0.03515 |
| Opus 5 | $0.01758 | $0.01758 |
| Sonnet 5 | $0.00703 | $0.00703 |
| Haiku 4.5 | $0.00351 | $0.00351 |
Grade A, and why
mcpproxy-go 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude Code / AI agents working in this repo. This file is loaded into every session and every Paperclip heartbeat — keep it lean. It is orientation + behavior only; detailed reference lives in docs/.
Autonomous Operation Constraints
Must-Do (Defaults & Assumptions)
- Zero Interruption Policy: If a decision is needed and no explicit instruction exists, make an informed, safe assumption based on idiomatic Go best practices and document it in the PR/commit. Do NOT ask for human clarification mid-task.
- Test-Driven Progress: Write a failing Go test (
_test.go) for every sub-task before implementing the feature. - Graceful Fallbacks: If an API or dependency lacks documentation, use mock interfaces or a simplified implementation rather than blocking the task.
Must-Nots
- Do NOT ask for plan approval: Once a plan/spec is generated, begin execution immediately.
- Do NOT stop for code style choices: Run
gofmt/goimportsand follow standard Go conventions.
Escalation Triggers (Stop Conditions)
Only halt and ask a human IF:
- You need destructive data operations or to delete core proxy logic that cannot be mocked.
- A required environment variable is missing from
.envand cannot be mocked for the task's scope. - You are stuck in an error loop for the same
go testfailing after 5 consecutive attempts. - Cross-model (Codex) review round cap — per PR: when a PR is gated by a cross-model Codex review, run at most 5 fix→re-review rounds on that PR. If Codex has not returned a clean verdict after the 5th round, STOP and ask the human how to proceed (do not auto-run round 6). The counter is per-PR and resets for each new PR. (Verify each Codex finding is genuine before fixing — Codex can false-positive; a round only counts when you push a fix and re-review.)
Project Overview
MCPProxy is a Go desktop application that acts as a smart proxy for AI agents using the Model Context Protocol (MCP): intelligent tool discovery, massive token savings, and built-in security quarantine against malicious MCP servers.
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 · 165 lines · 3,515 tokens per session scan A 680d508e34ad
mcpproxy-go CLAUDE.md is an instructions file published in the GitHub repository smart-mcp-proxy/mcpproxy-go (326 stars, last pushed 3d ago), licensed MIT. It adds 3,515 tokens to every session, about $0.0176 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
TitanX AGENTS.md
Instructions for CES-Ltd/TitanX, covering aionui - project guide, code conventions, file & directory structure, naming and ui library & icons.
mcpkernel copilot-instructions.md
Copilot instructions for piyushptiwari1/mcpkernel, covering mcpkernel — project context for all agents, project overview, architecture, code standards and build & test.
nomos CLAUDE.md
Instructions for safe-agentic-world/nomos, covering claude.md, commands, architecture, package map and conventions to preserve.
nomos AGENTS.md
Instructions for safe-agentic-world/nomos, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
mcpkernel testing-guidelines.instructions.md
Use when writing or modifying tests for MCPKernel. Covers pytest patterns, async testing, fixtures, and test structure.
mcpkernel policy-writing.instructions.md
Use when working with MCPKernel YAML policy files. Covers policy syntax, rule structure, OWASP ASI mappings, and best practices for writing security policies.