http-toolkit-intercept — Claude Code skill
http-toolkit-intercept captures HTTP requests and responses from any script or service — including LLM API calls, backend requests, and auth flows. Use it when you need to see what's actually sent over the wire and what comes back.
no license 124 installs ★ 129 updated 2026-10-25
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a claude-codeWhat http-toolkit-intercept does
This skill integrates HTTP Toolkit into a running process to inspect all network traffic. It works with Node.js, Python, Go, Java, Ruby, .NET, Rust, curl, and other runtimes that respect proxy environment variables. The typical workflow is: start HTTP Toolkit, run your program through the proxy at http://127.0.0.1:8000 with HTTP_PROXY, HTTPS_PROXY, and NO_PROXY set, capture the program's structured logs (if it supports --output-format json or similar), export the HTTP session from Toolkit, and cross-reference the two.
On Linux headless systems, use xvfb-run --auto-servernum httptoolkit --no-sandbox to avoid X11 sandbox errors. Each runtime has its own proxy quirks: Bun ignores standard env vars and requires BUN_CONFIG_PROXY; Java needs JVM flags -Dhttp.proxyHost and -Dhttp.proxyPort at startup. TLS verification is on by default — disable it with NODE_TLS_REJECT_UNAUTHORIZED=0 or runtime-specific equivalents only for local debugging when the HTTP Toolkit CA is not in your system trust store.
What it helps with
- inspect API calls to LLM services during integration development
- trace request payloads and headers in complex network flows
- debug authentication failures and auth header issues
- verify what data leaves your application before production deployment
- gather evidence of HTTP client behavior across different runtimes
Example prompts for the agent
- Capture HTTP requests from a Python script calling Claude API and examine headers and body content
- Run a Node.js app through HTTP Toolkit proxy and export logs in JSON to verify what data goes to your backend
- Debug a Go service by routing traffic through the proxy and matching outbound requests to application logs
How to install http-toolkit-intercept
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a claude-code2Manually: put the files in place
~/.claude/skills/http-toolkit-intercept/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/http-toolkit-intercept/
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a codex2Manually: put the files in place
.agents/skills/http-toolkit-intercept/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a cursor2Manually: put the files in place
.cursor/skills/http-toolkit-intercept/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Factory-AI/factory-plugins plugins/debugging/skills/http-toolkit-intercept2Manually: put the files in place
.github/skills/http-toolkit-intercept/SKILL.md1Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a gemini-cli2Platform CLI
gemini skills install https://github.com/Factory-AI/factory-plugins --path plugins/debugging/skills/http-toolkit-interceptManually: put the files in place
.devin/skills/http-toolkit-intercept/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about http-toolkit-intercept
How do I install http-toolkit-intercept for Claude Code?
Run npx skills add Factory-AI/factory-plugins --skill http-toolkit-intercept -a claude-code, then open ~/.claude/skills/http-toolkit-intercept/SKILL.md to get started. The skill requires HTTP Toolkit installed and access to ports 45456 and 45457.
What does http-toolkit-intercept do?
It wires HTTP Toolkit into your running processes to capture and inspect all HTTP traffic—requests, responses, headers, body content, auth tokens, and retry timing. All this happens on your development machine without modifying your code.
Which runtimes are supported?
Node.js, Bun, Deno, Python, Go, Ruby, Java/JVM, .NET, PHP, Rust, shell, and curl. Each honors different proxy environment variables: most respond to HTTP_PROXY and HTTPS_PROXY, but Bun requires BUN_CONFIG_PROXY and Java requires JVM flags like -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=8000.