code-explainer-mcp CLAUDE.md

Repository instructions for a code-explaining MCP server, a standard way for AI tools to access project functions. The server runs on Cloudflare Workers and explains source code using pattern matching.

In plain words
What is it for?
Use it when developing, testing, deploying, or regenerating types for this Cloudflare Worker project, and when reviewing how its code-explanation server works.
Why use it?
It gives a coding agent the project layout, commands, tests, and implementation details it should follow. This reduces guesswork when changing or checking the server.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/billduke13/code-explainer-mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/BillDuke13/code-explainer-mcp
Per session 925 This file is loaded in full into every session.
When invoked 925 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00925 $0.00925
Opus 5 $0.00463 $0.00463
Sonnet 5 $0.00185 $0.00185
Haiku 4.5 $0.00093 $0.00093

Measured 2d ago against content hash 16225bcb9571, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-explainer-mcp 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.

CLAUDE.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 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

MCP (Model Context Protocol) server running as a Cloudflare Worker. It explains source code (ASCII architecture diagram, core functionality, component breakdown) using regex/pattern matching only — no LLM calls and no external runtime dependencies. All logic lives in the single file src/index.ts: the default fetch export authenticates the request and dispatches to the module-private explainCode function and its helpers. There is no WorkerEntrypoint class (see "MCP tooling" below).

Commands

  • Dev server: npm run dev (alias npm start) — wrangler dev on http://localhost:8787
  • Deploy: npm run deploy — runs workers-mcp docgen src/index.ts then wrangler deploy
  • Regenerate binding types: npm run cf-typegen (wrangler types) — run after changing bindings/vars in wrangler.jsonc; it rewrites worker-configuration.d.ts
  • Tests: npm test (Vitest run via @cloudflare/vitest-pool-workers; npm run test:watch for watch mode) — the suite in test/index.spec.ts drives the Worker through SELF.fetch (info page incl. HEAD, auth + fail-closed guard, the explainCode contract for JS/Python, request validation). The test secret is injected via vitest.config.mts (miniflare bindings), overriding the placeholder.
  • Typecheck: no script — npx tsc --noEmit checks src/ (root tsconfig.json excludes test/); type-check the tests with npx tsc -p test/tsconfig.json --noEmit
  • Lint: npm run lint (eslint .); auto-fix with npm run lint:fix
  • Format: no script — use npx prettier --write . (a Write|Edit hook in .claude/settings.json also formats changed files)

MCP tooling (known discrepancy)

Despite the project name, src/index.ts does not use workers-mcp at runtime: it implements the endpoint directly with a default fetch export and a custom { method, params } body, not the MCP JSON-RPC wire protocol. workers-mcp is a devDependency (build/deploy-time only) and npm run deploy still runs workers-mcp docgen src/index.ts before wrangler deploy, but there is no WorkerEntrypoint class for docgen to derive tool schemas from. Treat the dependency and the docgen step as vestigial unless the Worker is rewritten onto WorkerEntrypoint. The function-level JSDoc in src/index.ts is ordinary documentation — keep it accurate, but docgen does not consume it today.

Read the full file on GitHub · 45 lines

Changes

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.

  1. 2d ago First seen · 45 lines · 925 tokens per session scan A 16225bcb9571

Subscribe to this mod's changes

code-explainer-mcp CLAUDE.md is an instructions file published in the GitHub repository BillDuke13/code-explainer-mcp (8 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 925 tokens to every session, about $0.0046 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.

Related

Other instructions, from other repositories

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.

github/spec-kit · 7,104 tokens

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).

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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).

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens