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/vltansky/explain-changes-mcp/claude-mdgit clone --depth 1 https://github.com/vltansky/explain-changes-mcpWhat 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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
explain-changes-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.
How it starts
The opening of the file, as written. The whole thing — 82 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 Structure
Monorepo with two packages:
packages/mcp- MCP server that provides theshow_diff_explanationtoolpackages/extension- VS Code/Cursor extension that displays diff explanations in a webview panel
Commands
# Root commands
npm run build # Build all packages
npm run build:mcp # Build MCP server only
npm run build:extension # Build extension only
# Extension (from packages/extension)
npm run dev # Dev server at http://localhost:3457 for webview debugging
npm run watch # Watch mode for extension development
npm run package # Create .vsix file
# MCP (from packages/mcp)
npm run build # Compile TypeScript to dist/
npm run start # Run MCP server via stdio
Architecture
MCP Server VS Code Extension
│ │
│ writes JSON to │ watches
│ ~/.explain-changes/ │ ~/.explain-changes/
│ pending.json │ pending.json
│ │
└──────────────────────────────┘
│
▼
Webview Panel
(renders diff + annotations)
MCP Package (packages/mcp)
src/index.ts- MCP server entry point. Registers tool and prompt, writes JSON to~/.explain-changes/pending.json
Extension Package (packages/extension)
src/extension.ts- Extension entry point. Watches pending.json, auto-configures MCP in Cursor/Windsurfsrc/webviewProvider.ts- Creates webview panel, renders diff with diff2html, handles button clickssrc/types.ts- Shared TypeScript typesdev/server.mjs- Dev server for debugging webview in browser with mock data and HMR
Tool Schema
The show_diff_explanation tool accepts:
title(required): Page titlediff(required): Raw git diff output (unified format)summary: High-level overviewannotations: Array of{ file, line?, explanation, actions? }workspacePath: Absolute path to project (for workspace filtering)editor:"cursor"|"vscode"
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 · 82 lines · 695 tokens per session scan A 50d5bba56a6b
explain-changes-mcp CLAUDE.md is an instructions file published in the GitHub repository vltansky/explain-changes-mcp (3 stars, last pushed 8mo ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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.
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).
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.