Burp Project Parser lets an agent query .burp project files without opening Burp’s GUI. It runs a wrapper script around Burp Suite Professional and the burpsuite-project-file-parser extension to search response headers and bodies with regex, list audit findings, and read proxy history or the site map.
The skill is built around context safety and trustworthy empty results. It tells the agent to start with headers, count bytes before retrieving anything, truncate bodies to 1000 characters, and treat exit codes 3 and 4 as unverified, never as proof that no traffic matched.
What You Get
- A wrapper script, burp-search.sh, with platform defaults for the Burp JRE and JAR on macOS and Linux
- Sub-component filters for request and response headers and bodies in proxy history and the site map
- Audit item extraction with severity and confidence triage guidance
- A control-query procedure that separates a true empty result from an unloaded extension
Common Use Cases
- Finding every response that sets or omits a security header across captured traffic
- Listing high-severity, high-confidence scanner findings from a finished Burp project
- Searching response bodies for a pattern such as a form action or leaked token
- Mapping the URLs seen in proxy history before deeper manual testing
What Makes It Unique
Most Burp helpers read the GUI or export files. This one works headless on the project file and is written around failure modes: Burp silently ignores flags when the extension is missing, so the wrapper script classifies output and exits with distinct codes, and the skill forbids reporting a clean result until a control query succeeds.
Under The Hood
The skill loads one instruction file and runs a bash wrapper that launches Burp Suite’s bundled Java with the project file, in headless mode, and filters the output through awk so only JSON reaches the agent. It runs shell commands and Java on your machine, reads the .burp file you name, and sends non-JSON lines to stderr with a cap on their length and count. It does not write files, call web APIs or fetch pages. You need Burp Suite Professional, the parser extension, and the BURP_JAVA and BURP_JAR variables where the defaults do not apply.