Automated summary
Inspect captured HTTP traffic from a MITM proxy by querying a REST API to list, filter, and view request/response details.
Strengths
- Filtering by URL substring
- Full view of request/response headers and bodies
- Export as HAR for external tools
- Clear history support
Limitations
- Requires MITM proxy running on localhost:8889
- Only works with intercepted traffic
- No WebSocket support
When debugging network calls during development or testing.
When real-time traffic monitoring is needed or MITM proxy is not set up.
Security analysis
SafeThe skill only queries a local MITM proxy API on localhost for legitimate traffic inspection and uses bundled bash scripts. No destructive actions, exfiltration, or external network calls. The use of user-provided filter argument is low risk and handled by curl's query string.
No concerns found
How this analysis is madeExamples
Show me the last 10 HTTP requests captured by the MITM proxy.List all captured requests that contain api.example.com in the URL.Show me the full details of request ID 5 from the proxy, including headers and body.name: mitm-inspect description: Inspect captured HTTP traffic from the MITM proxy. Use when the user wants to see what requests were made, filter traffic by URL, view request/response details, or analyze network activity. argument-hint: "[filter-pattern]" allowed-tools: Bash(bash *) Bash(curl *)
Inspect Captured Traffic
Use the MITM proxy REST API to list, filter, and inspect intercepted HTTP requests.
Arguments: $ARGUMENTS is an optional filter pattern (substring match on URL).
List requests
curl -s "http://localhost:8889/api/requests?filter=$ARGUMENTS&limit=20" | cat
Query params:
| Param | Type | Default | Description |
|-------|------|---------|-------------|
| filter | string | (none) | Substring match on request URL |
| limit | number | 100 | Max results to return |
| offset | number | 0 | Pagination offset |
Response shape:
{
"total": 42,
"offset": 0,
"limit": 20,
"requests": [
{
"id": 1,
"method": "GET",
"url": "https://api.example.com/users",
"status": 200,
"duration": 145,
"size": 2048,
"timestamp": "2026-02-14T12:00:00.000Z",
"modified": false,
"blocked": false,
"redirected": false,
"transformed": false
}
]
}
Get request detail
curl -s http://localhost:8889/api/requests/<ID> | cat
Replace <ID> with the numeric request ID from the list.
Response shape:
{
"id": 1,
"method": "GET",
"url": "https://api.example.com/users",
"timestamp": "2026-02-14T12:00:00.000Z",
"duration": 145,
"modified": false,
"blocked": false,
"redirected": false,
"redirectTarget": null,
"transformed": false,
"request": {
"headers": { "host": "api.example.com", "accept": "*/*" },
"body": ""
},
"response": {
"status": 200,
"headers": { "content-type": "application/json" },
"body": "{\"users\":[...]}"
}
}
Clear request history
curl -s -X DELETE http://localhost:8889/api/requests | cat
Response: { "cleared": true }
Bundled scripts
Traffic summary
Get a breakdown of captured traffic by domain, status code, and timing:
bash skills/mitm-inspect/scripts/traffic-summary.sh "$ARGUMENTS"
Outputs domain counts, status code distribution, average/max duration, and modification stats.
Export as HAR
Export captured requests to a HAR-like JSON file for external tools:
bash skills/mitm-inspect/scripts/export-har.sh "$ARGUMENTS" 100 mitm-export.json
Arguments: [filter] [limit] [output-file]
Typical workflow
- List recent traffic —
curl -s "http://localhost:8889/api/requests?limit=10" - Filter by domain —
curl -s "http://localhost:8889/api/requests?filter=api.example.com" - Inspect a specific request —
curl -s http://localhost:8889/api/requests/5 - Check request/response bodies — look at
.request.bodyand.response.bodyfields - Get a traffic summary —
bash skills/mitm-inspect/scripts/traffic-summary.sh - Export for analysis —
bash skills/mitm-inspect/scripts/export-har.sh - Clear old traffic —
curl -s -X DELETE http://localhost:8889/api/requests
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/mitm-traffic-inspection-mm78nnqj' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/mitm-traffic-inspection-mm78nnqj/download' --output '.skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md.part' && mv '.skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md.part' '.skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Bash(bash *) Bash(curl *)
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md' && test -s '.skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/mitm-inspect' && cp -R '.skill-downloads/mitm-traffic-inspection-mm78nnqj' '.claude/skills/mitm-inspect'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/mitm-traffic-inspection-mm78nnqj'openskills read 'mitm-traffic-inspection-mm78nnqj'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/mitm-traffic-inspection-mm78nnqj/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
ClickHouse Performance Comparison
Testing
Evaluate ClickHouse performance test results, check PR performance changes, compare with history, and assess whether a result is actionable.
Analyze CI Performance Reports
Testing
Analyze CI performance comparison reports for a ClickHouse PR. Cross-references master history to distinguish real regressions from flaky tests.
Santa Method
Testing
Multi-agent adversarial verification with two independent reviewers. Output is checked twice and iteratively fixed until both pass before shipping.