browser-auth-testing

Tests browser-based authentication flows and web vulnerabilities using Playwright MCP browser automation.

1|Updated Aug 21, 2026
One-click install
npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill browser-auth-testing-marcboggs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-auth-testing
Source: https://github.com/marcboggs/BMAD-AppSec-Orchestrator/tree/main/.claude/skills/browser-auth-testing
Command: npx skills add https://github.com/marcboggs/BMAD-AppSec-Orchestrator --skill browser-auth-testing-marcboggs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Testing login flows, OAuth redirects, session handling, and DOM-based vulnerabilities in JavaScript-heavy web applications is impossible with curl or Burp alone because they cannot maintain real browser state or execute client-side JavaScript. ## Core Features & Use Cases - Authentication Workflow Automation: Automate login sequences, save and reuse session state, and test MFA flows including bypass attempts via direct navigation. - Session & Cookie Analysis: Inspect Secure, HttpOnly, and SameSite cookie attributes, and audit localStorage/sessionStorage for exposed tokens and secrets. - Interactive Vulnerability Validation: Confirm DOM-based XSS, clickjacking, CSRF, and OAuth redirect manipulation with screenshots, console logs, and network captures as evidence. - Use Case: When a target SPA requires a multi-step login before any endpoint is reachable, use this Skill to authenticate via Playwright, save the storage state, then run authenticated scans and validate DOM XSS payloads that only execute in a real browser. ## Quick Start Use Playwright to log into the target application, save the session state, and test the session cookies for missing HttpOnly and SameSite flags.

Frequently Asked Questions about browser-auth-testing

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

FAQPage Schema
How do I test login flows in a JavaScript SPA during a pentest?▼

Use Playwright MCP tools to navigate to the login page, snapshot the form to identify field refs, type credentials, click submit, and wait for an authenticated-state indicator. Then save the session with browser_storage_state for reuse across tests.

When should I use Playwright instead of Burp or curl for web testing?▼

Use Playwright for JS-heavy SPAs, OAuth/SAML browser redirects, DOM XSS confirmation, clickjacking proofs, and cookie/localStorage inspection. Use Burp or curl for simple API probing, request smuggling, and header manipulation like Host or CL/TE attacks.

How do I confirm DOM-based XSS that Burp cannot detect?▼

Navigate to the URL with the payload in the fragment or query string, then use browser_evaluate to check whether the injected element exists or a marker like window.__xss_fired was set. Capture console messages and a screenshot as execution evidence.

Can Playwright test OAuth redirect_uri manipulation?▼

Yes. Navigate to the OAuth authorize endpoint, capture the full redirect chain with browser_network_requests, then use browser_route to intercept and modify the redirect_uri. Check whether the token is delivered to an attacker-controlled URI.

What session cookie misconfigurations should I check during testing?▼

Check that Secure is set on HTTPS targets, HttpOnly is present so XSS cannot steal the session, SameSite is not None without CSRF protection, path scope is not overly broad, and expiry is not persistent on shared devices.

What are the limitations of browser-based testing with Playwright?▼

Playwright cannot perform raw protocol attacks like request smuggling or low-level header manipulation, which require Burp or curl. It is also slower than direct HTTP tooling, so it should be reserved for workflows requiring real browser state.