Borrowing it
Nothing to install: this file belongs to KKonstantinov/graphql2mcp. 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/KKonstantinov/graphql2mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/KKonstantinov/graphql2mcpWrote 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/kkonstantinov/graphql2mcp/claude-md)<a href="https://agentmods.dev/instructions/kkonstantinov/graphql2mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/kkonstantinov/graphql2mcp/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.00528 | $0.00528 |
| Opus 5 | $0.00264 | $0.00264 |
| Sonnet 5 | $0.00106 | $0.00106 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
graphql2mcp 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 7d 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 — 67 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.
Project Overview
graphql2mcp converts GraphQL schemas and endpoints into MCP (Model Context Protocol) servers. Monorepo with pnpm workspaces.
Common Commands
pnpm build # Build all packages (tsdown)
pnpm test # Run all unit tests (vitest)
pnpm test:watch # Watch mode
pnpm test:integration # Build + run integration tests
pnpm lint # ESLint (includes Prettier checks)
pnpm lint:fix # ESLint with auto-fix
pnpm format # Prettier --write
pnpm typecheck # TypeScript type checking
Run for a specific package:
pnpm --filter graphql2mcp test
pnpm --filter @graphql2mcp/core test
pnpm --filter @graphql2mcp/lib test
Run a single test file:
pnpm vitest run packages/core/test/unit/example.test.ts
Architecture
Package Structure
packages/core/— Shared conversion engine (@graphql2mcp/core). GraphQL schema parsing → MCP tool definitionspackages/proxy/— Standalone proxy (graphql2mcp). CLI + server that proxies a GraphQL endpoint as an MCP serverpackages/lib/— Library (@graphql2mcp/lib). For integrating into existing TypeScript MCP servers
Both proxy and lib depend on core via workspace:*.
Code Conventions
- ESM only — all imports use
.jsextension (TypeScript ESM convention) - No
as any— use proper type guards - Prettier: 140 char width, 4-space indent, single quotes, no trailing commas,
arrowParens: "avoid" - Enforce
import typefor type-only imports
Testing Conventions
- Test through the public API when possible
- Use
toContainfor flexible output assertions (avoids whitespace brittleness) - Use
toBeonly for exact formatting tests - Unit tests in
test/unit/, integration tests intest/integration/
After Making Changes
Always run lint, typecheck, and tests before considering a change complete:
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.
- 7d ago First seen · 67 lines · 528 tokens per session scan A 3fc56def20be
graphql2mcp CLAUDE.md is an instructions file published in the GitHub repository KKonstantinov/graphql2mcp (1 stars, last pushed 4mo ago), licensed MIT. It adds 528 tokens to every session, about $0.0026 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
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.