security-burpsuite-project-parser

Parse Burp Suite XML exports to extract HTTP history and findings.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill security-burpsuite-project-parser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-burpsuite-project-parser
Source: https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents/tree/main/packages/skills/skills/security-burpsuite-project-parser
Command: npx skills add https://github.com/balic-AI-ML-R-D-Resources/eliza_autonomous_agents --skill security-burpsuite-project-parser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Burp Suite exports produce large, hard-to-navigate security findings and HTTP histories. This Skill provides a reliable parser to extract, deduplicate, and organize findings for faster triage and remediation.

Core Features & Use Cases

  • Parse Burp XML export to extract items, requests, responses, and findings
  • Deduplicate findings by URL, endpoint, and vulnerability type
  • Map findings to potential source code locations and generate structured reports
  • Use Case: Convert Burp findings into SARIF or CSV for integration with CI pipelines and ticketing systems

Quick Start

Feed a Burp XML export into the parser to produce a structured findings report.

Frequently Asked Questions about security-burpsuite-project-parser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parse Burp Suite XML exports to extract HTTP history and findings?

Parsing Burp Suite XML exports involves feeding the file into a specialized parser to extract HTTP history, request/response data, and findings for analysis. This structured extraction enables faster triage and remediation.

Can I convert Burp Suite findings into SARIF or CSV for CI pipelines?

Yes, you can convert Burp Suite findings into SARIF or CSV formats for integration with CI pipelines and ticketing systems. This allows security findings to be mapped to source endpoints and structured for automated reporting.

How do I deduplicate Burp Suite findings by URL and vulnerability type?

Deduplicating Burp Suite findings requires parsing the XML export and organizing the data by URL, endpoint, and vulnerability type. This process eliminates redundant findings and generates a cleaner report for remediation.

What is the best way to map Burp Suite vulnerabilities to source code locations?

Mapping Burp Suite vulnerabilities to source code locations is achieved by parsing the XML export to correlate findings with source endpoints. This deterministic parsing provides structured reports for identifying root causes.

Does this parser handle large Burp Suite HTTP history exports?

Yes, the parser is designed to handle large Burp Suite exports that produce hard-to-navigate security findings and HTTP histories. It reliably extracts and organizes the data to make triage more manageable.

Can I use this to extract request and response data from Burp Suite scans?

Yes, you can extract request and response data from Burp Suite scans by parsing the XML export. The parser isolates these items to support detailed security analysis and vulnerability identification.