/burp-suite-testing
This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive
$ npx -y skills add zebbern/claude-code-guide --skill burp-suite-testing --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/burp-suite-testing
Context preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive
SKILL.md
burp-suite-testing.SKILL.mdname: burp-suite-testing
description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing.
metadata:
author: zebbern
version: "1.1"
Burp Suite Web Application Testing
Purpose
Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.
Inputs / Prerequisites
Required Tools
- Burp Suite Community or Professional Edition installed
- Burp's embedded browser or configured external browser
- Target web application URL
- Valid credentials for authenticated testing (if applicable)
Environment Setup
- Burp Suite launched with temporary or named project
- Proxy listener active on 127.0.0.1:8080 (default)
- Browser configured to use Burp proxy (or use Burp's browser)
- CA certificate installed for HTTPS interception
Editions Comparison
| Feature | Community | Professional | |---------|-----------|--------------| | Proxy | ✓ | ✓ | | Repeater | ✓ | ✓ | | Intruder | Limited | Full | | Scanner | ✗ | ✓ | | Extensions | ✓ | ✓ |
Outputs / Deliverables
Primary Outputs
- Intercepted and modified HTTP requests/responses
- Vulnerability scan reports with remediation advice
- HTTP history and site map documentation
- Proof-of-concept exploits for identified vulnerabilities
Core Workflow
Phase 1: Intercepting HTTP Traffic
Launch Burp's Browser
Navigate to integrated browser for seamless proxy integration:
1. Open Burp Suite and create/open project 2. Go to **Proxy > Intercept** tab 3. Click **Open Browser** to launch preconfigured browser 4. Position windows to view both Burp and browser simultaneously
Configure Interception
Control which requests are captured:
Proxy > Intercept > Intercept is on/off toggle
When ON: Requests pause for review/modification
When OFF: Requests pass through, logged to history
Intercept and Forward Requests
Process intercepted traffic:
1. Set intercept toggle to **Intercept on** 2. Navigate to target URL in browser 3. Observe request held in Proxy > Intercept tab 4. Review request contents (headers, parameters, body) 5. Click **Forward** to send request to server 6. Continue forwarding subsequent requests until page loads
View HTTP History
Access complete traffic log:
1. Go to **Proxy > HTTP history** tab 2. Click any entry to view full request/response 3. Sort by clicking column headers (# for chronological order) 4. Use filters to focus on relevant traffic
Phase 2: Modifying Requests
Intercept and Modify
Change request parameters before forwarding:
1. Enable interception: **Intercept on** 2. Trigger target request in browser 3. Locate parameter to modify in intercepted request 4. Edit value directly in request editor 5. Click **Forward** to send modified request
Common Modification Targets
| Target | Example | Purpose | |--------|---------|---------| | Price parameters | `price=1` | Test business logic | | User IDs | `userId=admin` | Test access control | | Quantity values | `qty=-1` | Test input validation | | Hidden fields | `isAdmin=true` | Test privilege escalation |
Example: Price Manipulation
POST /cart HTTP/1.1
Host: target.com
Content-Type: application/x-www-form-urlencoded
productId=1&quantity=1&price=100
# Modify to:
productId=1&quantity=1&price=1
Result: Item added to cart at modified price.
Phase 3: Setting Target Scope
Define Scope
Focus testing on specific target:
1. Go to **Target > Site map** 2. Right-click target host in left panel 3. Select **Add to scope** 4. When prompted, click **Yes** to exclude out-of-scope traffic
Filter by Scope
Remove noise from HTTP history:
1. Click display filter above HTTP history 2. Select **Show only in-scope items** 3. History now shows only target site traffic
Scope Benefits
- Reduces clutter from third-party requests
- Prevents accidental testing of out-of-scope sites
- Improves scanning efficiency
- Creates cleaner reports
Phase 4: Using Burp Repeater
Send Request to Repeater
Prepare request for manual testing:
1. Identify interesting request in HTTP history 2. Right-click request and select **Send to Repeater** 3. Go to **Repeater** tab to access request
Modify and Resend
Test different inputs efficiently:
1. View request in Repeater tab
2. Modify parameter values
3. Click Send to submit request
4. Review response in right panel
5. Use navigation arrows to review request history
Repeater Testing Workflow
Original Request:
GET /product?productId=1 HTTP/1.1
Test 1: productId=2 → Valid product response
Test 2: productId=999 → Not Found response
Test 3: productId=' → Error/exception response
Test 4: productId=1 OR 1=1 → SQL injection test
Analyze Responses
Look for indicators of vulnerabilities:
- Error messages revealing stack traces
- Framework/version information disclosure
- Different response lengths indicating logic flaws
- Timing differences suggesting blind injection
- Unexpected data in responses
Phase 5: Running Automated Scans
Launch New Scan
Initiate vulnerability scanning (Professional only):
1. Go to **Dashboard** tab 2. Click **New scan** 3. Enter target URL in **URLs to scan** field 4. Configure scan settings
Scan Configuration Options
| Mode | Description | Duration | |------|-------------|----------| | Lightweight | High-level overview | ~15 minutes | | Fast | Quick vul
Read more
name: burp-suite-testing description: This skill should be used when the user asks to "intercept HTTP traffic", "modify web requests", "use Burp Suite for testing", "perform web vulnerability scanning", "test with Burp Repeater", "analyze HTTP history", or "configure proxy for web testing". It provides comprehensive guidance for using Burp Suite's core features for web application security testing. metadata: author: zebbern version: "1.1"
Burp Suite Web Application Testing
Purpose
Execute comprehensive web application security testing using Burp Suite's integrated toolset, including HTTP traffic interception and modification, request analysis and replay, automated vulnerability scanning, and manual testing workflows. This skill enables systematic discovery and exploitation of web application vulnerabilities through proxy-based testing methodology.
Inputs / Prerequisites
Required Tools
- Burp Suite Community or Professional Edition installed
- Burp's embedded browser or configured external browser
- Target web application URL
- Valid credentials for authenticated testing (if applicable)
Environment Setup
- Burp Suite launched with temporary or named project
- Proxy listener active on 127.0.0.1:8080 (default)
- Browser configured to use Burp proxy (or use Burp's browser)
- CA certificate installed for HTTPS interception
Editions Comparison
| Feature | Community | Professional | |---------|-----------|--------------| | Proxy | ✓ | ✓ | | Repeater | ✓ | ✓ | | Intruder | Limited | Full | | Scanner | ✗ | ✓ | | Extensions | ✓ | ✓ |
Outputs / Deliverables
Primary Outputs
- Intercepted and modified HTTP requests/responses
- Vulnerability scan reports with remediation advice
- HTTP history and site map documentation
- Proof-of-concept exploits for identified vulnerabilities
Core Workflow
Phase 1: Intercepting HTTP Traffic
Launch Burp's Browser
Navigate to integrated browser for seamless proxy integration:
1. Open Burp Suite and create/open project 2. Go to **Proxy > Intercept** tab 3. Click **Open Browser** to launch preconfigured browser 4. Position windows to view both Burp and browser simultaneously
Configure Interception
Control which requests are captured:
Proxy > Intercept > Intercept is on/off toggle When ON: Requests pause for review/modification When OFF: Requests pass through, logged to history
Intercept and Forward Requests
Process intercepted traffic:
1. Set intercept toggle to **Intercept on** 2. Navigate to target URL in browser 3. Observe request held in Proxy > Intercept tab 4. Review request contents (headers, parameters, body) 5. Click **Forward** to send request to server 6. Continue forwarding subsequent requests until page loads
View HTTP History
Access complete traffic log:
1. Go to **Proxy > HTTP history** tab 2. Click any entry to view full request/response 3. Sort by clicking column headers (# for chronological order) 4. Use filters to focus on relevant traffic
Phase 2: Modifying Requests
Intercept and Modify
Change request parameters before forwarding:
1. Enable interception: **Intercept on** 2. Trigger target request in browser 3. Locate parameter to modify in intercepted request 4. Edit value directly in request editor 5. Click **Forward** to send modified request
Common Modification Targets
| Target | Example | Purpose | |--------|---------|---------| | Price parameters | `price=1` | Test business logic | | User IDs | `userId=admin` | Test access control | | Quantity values | `qty=-1` | Test input validation | | Hidden fields | `isAdmin=true` | Test privilege escalation |
Example: Price Manipulation
POST /cart HTTP/1.1 Host: target.com Content-Type: application/x-www-form-urlencoded productId=1&quantity=1&price=100 # Modify to: productId=1&quantity=1&price=1
Result: Item added to cart at modified price.
Phase 3: Setting Target Scope
Define Scope
Focus testing on specific target:
1. Go to **Target > Site map** 2. Right-click target host in left panel 3. Select **Add to scope** 4. When prompted, click **Yes** to exclude out-of-scope traffic
Filter by Scope
Remove noise from HTTP history:
1. Click display filter above HTTP history 2. Select **Show only in-scope items** 3. History now shows only target site traffic
Scope Benefits
- Reduces clutter from third-party requests
- Prevents accidental testing of out-of-scope sites
- Improves scanning efficiency
- Creates cleaner reports
Phase 4: Using Burp Repeater
Send Request to Repeater
Prepare request for manual testing:
1. Identify interesting request in HTTP history 2. Right-click request and select **Send to Repeater** 3. Go to **Repeater** tab to access request
Modify and Resend
Test different inputs efficiently:
1. View request in Repeater tab 2. Modify parameter values 3. Click Send to submit request 4. Review response in right panel 5. Use navigation arrows to review request history
Repeater Testing Workflow
Original Request: GET /product?productId=1 HTTP/1.1 Test 1: productId=2 → Valid product response Test 2: productId=999 → Not Found response Test 3: productId=' → Error/exception response Test 4: productId=1 OR 1=1 → SQL injection test
Analyze Responses
Look for indicators of vulnerabilities:
- Error messages revealing stack traces
- Framework/version information disclosure
- Different response lengths indicating logic flaws
- Timing differences suggesting blind injection
- Unexpected data in responses
Phase 5: Running Automated Scans
Launch New Scan
Initiate vulnerability scanning (Professional only):
1. Go to **Dashboard** tab 2. Click **New scan** 3. Enter target URL in **URLs to scan** field 4. Configure scan settings
Scan Configuration Options
| Mode | Description | Duration | |------|-------------|----------| | Lightweight | High-level overview | ~15 minutes | | Fast | Quick vul
Claude Code Guide - Setup, Commands, workflows, agents, skills & tips-n-tricks from beginner to power user!
Repo: zebbern/claude-code-guide
Other skills on claude-code-guide.
- /academic-paper-reviewer
Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to \"review my paper,\" \"simulate peer review,\" or \"give my paper a peer
Open skill - /active-directory-attacks
This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration
Open skill - /api-fuzzing-bug-bounty
This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.
Open skill - /api-shape-explorer
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Open skill - /audit-flow
Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems.
Open skill - /authentication-patterns
Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.
Open skill

