mcpField
M
mitm-report

mitm-report

github.com/instavmSecurity8770 installsUpdated 13w ago
Repository

About mitm-report

A security skill for producing vulnerability assessment reports from findings or a mitmproxy log. It gathers report details such as the target, findings, format, and whether to include reproduction steps.

Key features

  1. 01Creates security assessment reports
  2. 02Uses findings or mitmproxy logs
  3. 03Supports Markdown, HTML, or PDF outlines
  4. 04Collects target and reproduction-step preferences

Use cases

  1. 01Turn traffic-analysis findings into a report
  2. 02Prepare an assessment with reproduction steps
  3. 03Choose a report format for security findings

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/instavm/security-skills --skill mitm-report

After installing, type/mitm-reportin Claude Code to confirm it loaded.

Details

From the project README

Generate Security Vulnerability Report

Generate a security report based on findings. Format: $ARGUMENTS (default: markdown)

Requires: log.txt in the current directory (or findings from a previous skill run). If it's missing, capture traffic first:

mitmdump --set flow_detail=3 2>&1 | tee log.txt

Report Template

# Security Assessment Report

**Target**: [Application Name]
**Date**: [Assessment Date]
**Assessor**: [Name]

## Executive Summary

Brief overview of findings and overall security posture.

## Findings Summary

| # | Title | Severity | Status |
|---|-------|----------|--------|
| 1 | [Finding Title] | High | Open |

## Detailed Findings

### [APP] Finding Title
* **Severity**: `critical/high/medium/low/info`
* **Endpoint**: `https://example.com/api/endpoint`
* **Steps to Reproduce**:
  1. Step one
  2. Step two
  3. Verify with: `curl command here`
* **Impact**: Description of business/security impact
* **Remediation**: Specific steps to fix

## Severity Guidelines

- **CRITICAL**: RCE, full database access, admin takeover
- **HIGH**: Account takeover, payment bypass, mass data leak
- **MEDIUM**: PII leak, business logic bypass, limited data exposure
- **LOW**: Information disclosure, missing security headers
- **INFO**: Best practice violations, no direct impact

## Remediation Priorities

1. Critical and High - Immediate
2. Medium - Within 30 days
3. Low/Info - Next release cycle

## Testing Methodology

Description of tools and techniques used.

Before Generating

Ask for:

  • Target application name
  • Findings to include (or analyze from log.txt)
  • Output format preference (markdown/HTML/PDF outline)
  • Include reproduction steps? (yes/no)

Comments

Markdown supported