Burp Suite Web Application Testing workflow skill. Use this skill when the user needs 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 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
Burp Suite Web Application Testing workflow skill. Use this skill when the user needs 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 and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
This public intake copy packages plugins/antigravity-bundle-security-engineer/skills/burp-suite-testing from https://github.com/sickn33/antigravity-awesome-skills into the native Omni Skills editorial shape without hiding its origin.
Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow.
This intake keeps the copied upstream files intact and uses the external_source block in metadata.json plus ORIGIN.md as the provenance anchor for review.
AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments. # Burp Suite Web Application Testing
Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Purpose, Inputs / Prerequisites, Outputs / Deliverables.
When to Use This Skill
Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request.
This skill is applicable to execute the workflow or actions described in the overview.
Use when the request clearly matches the imported source intent: 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....
Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch.
Use when provenance needs to stay visible in the answer, PR, or review packet.
Use when copied upstream references, examples, or scripts materially improve the answer.
Use when the workflow should remain reviewable in the public intake repo before the private enhancer takes over.
Operating Table
Situation
Start here
Why it matters
First-time use
metadata.json
Confirms repository, branch, commit, and imported path through the external_source block before touching the copied workflow
Provenance review
ORIGIN.md
Gives reviewers a plain-language audit trail for the imported source
Workflow execution
SKILL.md
Starts with the smallest copied file that materially changes execution
Supporting context
SKILL.md
Adds the next most relevant copied source file without loading the entire package
Handoff decision
## Related Skills
Helps the operator switch to a stronger native skill when the task drifts
Workflow
This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow.
Open Burp Suite and create/open project
Go to Proxy > Intercept tab
Click Open Browser to launch preconfigured browser
Position windows to view both Burp and browser simultaneously
Set intercept toggle to Intercept on
Navigate to target URL in browser
Observe request held in Proxy > Intercept tab
Imported Workflow Notes
Imported: Core Workflow
Phase 1: Intercepting HTTP Traffic
Launch Burp's Browser
Navigate to integrated browser for seamless proxy integration:
Open Burp Suite and create/open project
Go to Proxy > Intercept tab
Click Open Browser to launch preconfigured browser
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
Continue forwarding subsequent requests until page loads
View HTTP History
Access complete traffic log:
Go to Proxy > HTTP history tab
Click any entry to view full request/response
Sort by clicking column headers (# for chronological order)
Use filters to focus on relevant traffic
Phase 2: Modifying Requests
Intercept and Modify
Change request parameters before forwarding:
Enable interception: Intercept on
Trigger target request in browser
Locate parameter to modify in intercepted request
Edit value directly in request editor
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:
Go to Target > Site map
Right-click target host in left panel
Select Add to scope
When prompted, click Yes to exclude out-of-scope traffic
Filter by Scope
Remove noise from HTTP history:
Click display filter above HTTP history
Select Show only in-scope items
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:
Identify interesting request in HTTP history
Right-click request and select Send to Repeater
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
Send request to Intruder (right-click > Send to Intruder)
Go to Intruder tab
Define payload positions using § markers
Select attack type
Attack Types
Type
Description
Use Case
Sniper
Single position, iterate payloads
Fuzzing one parameter
Battering ram
Same payload all positions
Credential testing
Pitchfork
Parallel payload iteration
Username:password pairs
Cluster bomb
All payload combinations
Full brute force
Configure Payloads
Positions Tab:
POST /login HTTP/1.1
...
username=§admin§&password=§password§
Payloads Tab:
Set 1: admin, user, test, guest
Set 2: password, 123456, admin, letmein
Analyze Results
Review attack output:
Sort by response length to find anomalies
Filter by status code for successful attempts
Use grep to search for specific strings
Export results for documentation
Imported: 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.
Examples
Example 1: Ask for the upstream workflow directly
Use @burp-suite-testing-v3 to handle <task>. Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer.
Explanation: This is the safest starting point when the operator needs the imported workflow, but not the entire repository.
Example 2: Ask for a provenance-grounded review
Review @burp-suite-testing-v3 against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why.
Explanation: Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection.
Example 3: Narrow the copied support files before execution
Use @burp-suite-testing-v3 for <task>. Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding.
Explanation: This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default.
Example 4: Build a reviewer packet
Review @burp-suite-testing-v3 using the copied upstream files plus provenance, then summarize any gaps before merge.
Explanation: This is useful when the PR is waiting for human review and you want a repeatable audit packet.
Imported Usage Notes
Imported: Examples
Example 1: Business Logic Testing
Scenario: E-commerce price manipulation
Add item to cart normally, intercept request
Identify price=9999 parameter in POST body
Modify to price=1
Forward request
Complete checkout at manipulated price
Finding: Server trusts client-provided price values.
Example 2: Authentication Bypass
Scenario: Testing login form
Submit valid credentials, capture request in Repeater
Send to Repeater for testing
Try: username=admin' OR '1'='1'--
Observe successful login response
Finding: SQL injection in authentication.
Example 3: Information Disclosure
Scenario: Error-based information gathering
Navigate to product page, observe productId parameter
Send request to Repeater
Change productId=1 to productId=test
Observe verbose error revealing framework version
Finding: Apache Struts 2.5.12 disclosed in stack trace.
Best Practices
Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution.
Test only authorized applications
Configure scope to prevent accidental out-of-scope testing
Rate-limit scans to avoid denial of service
Document all findings and actions
Community Edition lacks automated scanner
Some sites may block proxy traffic
HSTS/certificate pinning may require additional configuration
Imported Operating Notes
Imported: Constraints and Guardrails
Operational Boundaries
Test only authorized applications
Configure scope to prevent accidental out-of-scope testing
Rate-limit scans to avoid denial of service
Document all findings and actions
Technical Limitations
Community Edition lacks automated scanner
Some sites may block proxy traffic
HSTS/certificate pinning may require additional configuration
Heavy scanning may trigger WAF blocks
Best Practices
Always set target scope before extensive testing
Use Burp's browser for reliable interception
Save project regularly to preserve work
Review scan results manually for false positives
Troubleshooting
Problem: The operator skipped the imported context and answered too generically
Symptoms: The result ignores the upstream workflow in plugins/antigravity-bundle-security-engineer/skills/burp-suite-testing, fails to mention provenance, or does not use any copied source files at all.
Solution: Re-open metadata.json, ORIGIN.md, and the most relevant copied upstream files. Check the external_source block first, then restate the provenance before continuing.
Problem: The imported workflow feels incomplete during review
Symptoms: Reviewers can see the generated SKILL.md, but they cannot quickly tell which references, examples, or scripts matter for the current task.
Solution: Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it.
Problem: The task drifted into a different specialization
Symptoms: The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better.
Solution: Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind.
Imported Troubleshooting Notes
Imported: Troubleshooting
Browser Not Connecting Through Proxy
Verify proxy listener is active (Proxy > Options)
Check browser proxy settings point to 127.0.0.1:8080
@ab-test-setup-v5 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@api-security-best-practices-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@async-python-patterns-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
@auth-implementation-patterns-v3 - Use when the work is better handled by that native specialization after this imported skill establishes context.
Additional Resources
Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding.
Resource family
What it gives the reviewer
Example path
references
copied reference notes, guides, or background material from upstream
references/n/a
examples
worked examples or reusable prompts copied from upstream
examples/n/a
scripts
upstream helper scripts that change execution or validation
scripts/n/a
agents
routing or delegation notes that are genuinely part of the imported package
agents/n/a
assets
supporting assets or schemas copied from the source package
assets/n/a
Imported Reference Notes
Imported: Quick Reference
Keyboard Shortcuts
Action
Windows/Linux
macOS
Forward request
Ctrl+F
Cmd+F
Drop request
Ctrl+D
Cmd+D
Send to Repeater
Ctrl+R
Cmd+R
Send to Intruder
Ctrl+I
Cmd+I
Toggle intercept
Ctrl+T
Cmd+T
Common Testing Payloads
# SQL Injection
' OR '1'='1
' OR '1'='1'--
1 UNION SELECT NULL--
# XSS
<script>alert(1)</script>
"><img src=x onerror=alert(1)>
javascript:alert(1)
# Path Traversal
../../../etc/passwd
..\..\..\..\windows\win.ini
# Command Injection
; ls -la
| cat /etc/passwd
`whoami`
Request Modification Tips
Right-click for context menu options
Use decoder for encoding/decoding
Compare requests using Comparer tool
Save interesting requests to project
Imported: 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
✓
✓
Imported: 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
