Skip to content
SkillMixed4,174 tokens in use

Burp Project Parser

Searches and extracts data from Burp Suite project files from the command line, with strict size limits so traffic never floods the agent's context.

8,319 stars on the repository CC-BY-SA-4.0trailofbits/skills · plugins/burpsuite-project-parser/skills/burpsuite-project-parser
/plugin marketplace add trailofbits/skills
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Burp Project Parser costs

59tokens idle
4,174tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Mixed

Script-ledMixedModel-led

Scripts do part of the work and the model's judgement does the rest.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/burp-search.sh.

Touches

shelldeclared and detectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure25/25
  • Examples15/15
  • Output15/15
  • Size15/15
  • Resources0/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−2

    does this on the machine, as the frontmatter declares

    SKILL.md, line 35
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/burp-search.sh, line 46

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community64
  • Maturity32
  • Momentum40

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.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers