burpsuite-project-parser

Parse Burp Suite .burp project files to extract headers, audit items, proxy history, and site maps.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/DobricLilujun/LabAgentSkill --skill burpsuite-project-parser-dobriclilujun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: burpsuite-project-parser
Source: https://github.com/DobricLilujun/LabAgentSkill/tree/main/skillsHub/skills_scaling/burpsuite-project-parser/skills
Command: npx skills add https://github.com/DobricLilujun/LabAgentSkill --skill burpsuite-project-parser-dobriclilujun

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Burp Suite project files (.burp) hold rich security data, but manual searches are slow and error prone; this skill provides a CLI-driven way to locate and extract headers, audit items, proxy data, and site maps across Burp projects.

Core Features & Use Cases

  • Search and explore Burp project files: locate headers, audit items, proxy history, and site maps using targeted searches and regex.
  • Regex-based data extraction: pull specific fields (urls, headers, findings) for triage and remediation workflows.
  • Workflow integration: enables automation in CI/CD or security testing pipelines via a wrapper script and CLI.
  • Use Case: security engineers can scan a Burp project for high-severity findings and export a concise summary of affected URLs.

Quick Start

Run the burpsuite-project-parser to scan a Burp project file (e.g., project.burp) and extract headers, audit items, or proxy data matching a regex pattern.

Frequently Asked Questions about burpsuite-project-parser

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

FAQPage Schema
How do I extract proxy history and audit items from a Burp Suite project file?

To extract proxy history and audit items from a Burp Suite project file, use a CLI wrapper to parse the .burp file and apply regex patterns to retrieve specific security data like headers and site maps.

Can I search across multiple Burp projects for specific headers using regex?

Yes, you can search across multiple Burp projects using regex patterns to locate and extract specific headers, URLs, and findings, replacing slow manual searches with automated data extraction.

Do I need Burp Suite Professional to parse .burp project files?

Yes, parsing .burp project files requires the Burp Suite Professional extension along with a CLI wrapper to perform the structured queries and data extraction.

What is the best way to automate extracting high-severity findings from Burp projects in a CI/CD pipeline?

Automating extraction of high-severity findings in a CI/CD pipeline is best achieved by using a CLI wrapper to scan .burp project files and export concise summaries of affected URLs matching your regex criteria.

Are there limitations when parsing Burp site maps with regex patterns?

Limitations of parsing Burp site maps with regex patterns include potential mismatches in unstructured data, requiring precise pattern formulation to accurately extract targeted security signals without errors.

Why does manual searching in Burp Suite project files fail during triage workflows?

Manual searching in Burp Suite project files fails during triage workflows because it is slow and error prone, making regex-based data extraction via a CLI wrapper necessary for accurate remediation.