Borrowing it
Nothing to install: this file belongs to Kuadrant/mcp-gateway. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kuadrant/mcp-gateway/main/CLAUDE.mdgit clone --depth 1 https://github.com/Kuadrant/mcp-gatewayWrote 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.
[](https://agentmods.dev/instructions/kuadrant/mcp-gateway/claude-md)<a href="https://agentmods.dev/instructions/kuadrant/mcp-gateway/claude-md"><img src="https://agentmods.dev/badge/instructions/kuadrant/mcp-gateway/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.1 | $0.01277 | $0.01277 |
| Opus 5 | $0.00639 | $0.00639 |
| Sonnet 5 | $0.00255 | $0.00255 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
mcp-gateway 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Project Overview
MCP Gateway: an Envoy-based gateway for Model Context Protocol (MCP) servers.
Two binaries, four components:
cmd/mcp-broker-router/main.go — data-plane:
- Router: Envoy ext_proc, routes MCP requests (gRPC :50051)
- Broker: aggregates tools from upstream MCP servers (HTTP :8080/mcp)
cmd/main.go — control-plane:
- Controller: discovers MCP servers via MCPServerRegistration and MCPVirtualServer CRDs
- Operator: reconciles MCPGatewayExtension, deploys router + broker instances
Architecture
Client → Gateway (Envoy) → Router (ext_proc) → Broker → Upstream MCP Servers
↑ ↑
Controller → Secret ──────────────────┘
- Controller watches CRDs, discovers backends via HTTPRoutes, writes config Secret
- Broker reads config Secret, connects to upstreams, federates tools with prefixes
- Router parses MCP requests, adds auth headers, tells Envoy where to route
- Tool calls use lazy init: router hairpins an initialize request back through Envoy before the tool/call
- All MCP traffic flows through Envoy for consistent policies
Istio is ONLY a Gateway API provider — no sidecars, no ambient mode, no service mesh. Just istiod programming the Gateway's Envoy proxy.
TLS Trust Pool
Broker and 2025-11-25 hairpin TLS trust is additive:
- System roots — always loaded
- Gateway CA bundle —
MCPGatewayExtension.caCertBundleRefreferences a shared Secret, written once to config asgatewayCACertPEM. Used for broker→upstream connections and for 2025-11-25 protocol hairpin requests to the gateway HTTPS listener. 2026-07-28 MCP calls do not hairpin. If the listener CA and upstream CAs differ, concatenate both PEMs in that Secret. - Per-server CA —
MCPServerRegistration.caCertSecretRefappends for servers with unique CAs (upstream only, not hairpin)
Each layer appends to the previous. Gateway bundle changes trigger broker to recreate TLS upstream managers and rebuild the hairpin client.
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.
- 8d ago First seen · 116 lines · 1,277 tokens per session scan A 8b6fab5aa469
mcp-gateway CLAUDE.md is an instructions file published in the GitHub repository Kuadrant/mcp-gateway (98 stars, last pushed today), licensed Apache-2.0. It adds 1,277 tokens to every session, about $0.0064 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
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.
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).
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.
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).
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.