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/ephrin/openapi-mcp-bridge/claude-mdgit clone --depth 1 https://github.com/ephrin/openapi-mcp-bridgeWrote 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/ephrin/openapi-mcp-bridge/claude-md)<a href="https://agentmods.dev/instructions/ephrin/openapi-mcp-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/ephrin/openapi-mcp-bridge/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.01235 | $0.01235 |
| Opus 5 | $0.00617 | $0.00617 |
| Sonnet 5 | $0.00247 | $0.00247 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
openapi-mcp-bridge 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 5d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Development Commands
npm install- Install all dependenciesnpm run build- Compile TypeScript to JavaScript (outputs todist/)npm run dev- Run in development mode with hot-reloading using tsxnpm start- Run the compiled server from dist/npm run server- Run the HTTP-based development servernpm run lint- Run ESLint on TypeScript filesnpm run typecheck- Check TypeScript types without emitting files
Architecture Overview
This is an MCP (Model Context Protocol) server that dynamically exposes OpenAPI specifications as callable tools. The project supports multiple deployment modes: as a stdio-based MCP server, HTTP server, or integrated into Express/Koa/Fastify applications.
Core Architecture
The project follows a modular, service-oriented architecture:
- Definition Loading: OpenAPI specifications are loaded from a definitions directory
- Parsing & Enrichment: Specs are parsed, references resolved, and enriched with customizations
- Tool Generation: Each OpenAPI operation is converted to an MCP tool with proper schemas
- Request Execution: Tool calls are mapped back to HTTP API requests
- Response Handling: API responses are normalized and returned as tool results
Key Components
Core Service (src/services/mcp-proxy-service.ts)
- MCPProxyService: Orchestrates all functionality
- Loads and manages multiple OpenAPI definitions from a directory
- Converts OpenAPI operations to MCP tools via enrichers and converters
- Executes tool calls by mapping them to HTTP requests
- Handles authentication and parameter validation
Parsers (src/parsers/)
- OpenAPIDefinitionParser: Parses and validates OpenAPI 3.0 specifications
- Uses
@readme/openapi-parserfor reference resolution - Extracts paths, parameters, request bodies, and security schemes
- Uses
- CustomizationLoader: Loads
.custom.yamlfiles for per-definition configuration- Tool aliases and descriptions
- Predefined parameters
- Authentication credentials
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.
- 5d ago First seen · 146 lines · 1,235 tokens per session scan A 9514dd7fb2ff
openapi-mcp-bridge CLAUDE.md is an instructions file published in the GitHub repository ephrin/openapi-mcp-bridge (1 stars, last pushed 1y ago), licensed MIT. It adds 1,235 tokens to every session, about $0.0062 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-31.
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.
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.
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).