by kangraemin
Claude Code Prompt Mechanism Visualizer — Electron desktop app
# Add to your Claude Code skills
git clone https://github.com/kangraemin/claude-inspectorSee what Claude Code actually sends to the API.
MITM proxy that intercepts Claude Code CLI traffic in real-time<br> and visualizes all 5 prompt augmentation mechanisms.
Install · What You'll Learn · Proxy Mode · Tech Stack
English | 한국어
</div>All discovered from real captured traffic. See what Claude Code hides from you.
You type hello. Claude Code silently prepends ~12KB before your message:
| Block | What's inside | Size |
|-------|--------------|------|
| content[0] | Available skills list | ~2KB |
| content[1] | CLAUDE.md + rules + memory | ~10KB |
| content[2] | What you actually typed | few bytes |
No comments yet. Be the first to share your thoughts!
Injection order: Global CLAUDE.md → Global rules → Project CLAUDE.md → Memory
This ~12KB payload is re-sent with every request. A 500-line CLAUDE.md quietly burns tokens on every API call. Keep it lean.
tools[] growBuilt-in tools (27) ship their full JSON schemas every request. MCP tools don't — they start as names only.
Watch the count change in real-time:
| Step | What happens | tools[] count |
|------|-------------|-----------------|
| Initial request | 27 built-in tools loaded | 27 |
| Model calls ToolSearch("context7") | Full schema for 2 MCP tools returned | 29 |
| Model calls ToolSearch("til") | 6 more MCP tool schemas added | 35 |
Unused MCP tools never consume tokens. The Inspector lets you watch tools[] grow as the model discovers what it needs.
When Claude Code reads a screenshot or image file, the image is base64-encoded and embedded directly in the JSON body:
{
"type": "image",
"source": {
"type": "base64",
"media_type": "image/png",
"data": "iVBORw0KGgo..."
}
}
A single screenshot can add hundreds of KB to the request payload. The Inspector shows you the exact size.
Typing /something triggers one of three completely different mechanisms:
| | Local Command | User Sk...