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 skills/moha-abdi/mitmproxy-mcp/mitmproxy-mcpnpx skills add moha-abdi/mitmproxy-mcp --skill mitmproxy-mcpgit clone --depth 1 https://github.com/moha-abdi/mitmproxy-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/moha-abdi/mitmproxy-mcp/mitmproxy-mcp)<a href="https://agentmods.dev/skills/moha-abdi/mitmproxy-mcp/mitmproxy-mcp"><img src="https://agentmods.dev/badge/skills/moha-abdi/mitmproxy-mcp/mitmproxy-mcp.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00059 | $0.01187 |
| Opus 5 | $0.00030 | $0.00593 |
| Sonnet 5 | $0.00012 | $0.00237 |
| Haiku 4.5 | $0.00006 | $0.00119 |
Grade A, and why
mitmproxy-mcp 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 6d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mitmproxy-mcp
HTTP/HTTPS traffic analysis, interception, and replay through mitmproxy.
Prerequisites
- mitmproxy running with the mitmproxy-mcp addon loaded
- MCP server available at
http://localhost:9011/sse(SSE transport)
If the MCP server is not connected, tell the user to start mitmproxy first:
mitmproxy # or mitmweb, or mitmdump
The addon and MCP server start automatically if configured in ~/.mitmproxy/config.yaml.
For dependency-safe startup, install shims once with mitmproxy-mcp install-shims --force.
When to Use This Skill
- User asks to inspect, debug, or analyze HTTP traffic
- User wants to replay or modify an HTTP request
- User wants to intercept requests matching a pattern
- User needs to export captured traffic (HAR format)
- User is doing API debugging or security testing
Available Tools (20)
Flow Tools -- querying captured traffic
get_flows-- list captured flows with optional filtering by method, URL pattern, or status code. Supportslimitandoffsetfor pagination.get_flow_by_id-- get full request and response details for a single flowsearch_flows-- search flows by regex pattern across URL, method, status, and headersget_flow_request-- get only the request portion of a flowget_flow_response-- get only the response portion of a flowget_flow_count-- count of currently stored flowsclear_flows-- clear all stored flows and clear mitmproxy's flow view when sync includesclearexport_flows-- export flows to HAR 1.2 format. Optionally pass specific flow IDs.
Replay Tools -- sending and modifying requests
replay_request-- replay a captured request exactly as-is. Replays in-place when view sync includesreplay; otherwise creates a detached replay flow.send_request-- send a new HTTP request. Parameters:url(required),method(default GET),headers,body.modify_and_send-- take an existing flow, change its method/url/headers/body, and send it. Useful for testing variations.duplicate_flow-- clone a flow without sending it. Useful for before/after comparisons.
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.
- 6d ago First seen · 99 lines · 59 tokens per session scan A 409a8581e134
mitmproxy-mcp is a skill published in the GitHub repository moha-abdi/mitmproxy-mcp (9 stars, last pushed 6mo ago), licensed MIT. It adds 59 tokens to every session and 1,187 once invoked, about $0.0003 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 skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…