skills/reflected-xss/SKILL.md
Use when attacker-controlled input appears in the immediate HTTP response or browser-rendered page and needs reflected XSS context classification, payload selection, mutation, and browser verification.
npx skillsauth add ghostonbutterbread/bug-bounty-harness reflected-xssInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Use this lane when a marker reflects immediately in the response or rendered page.
The goal is to identify the exact output context, break that context with the smallest useful payload, then mutate as needed until execution is proven or a real boundary appears.
xsslive-testing-policywaf-live-policy if filters, bot defenses, WAF, sanitizers, or parser quirks
shape the testskills/xss/references/payload-selection.mdCheck more than query parameters when evidence supports it:
Referer, User-Agent, X-Forwarded-*, custom app headersRecord where the marker lands:
Do not choose payloads before context classification.
Prefer reasoning like:
< but leaves quotes, so attribute injection may still
work."innerHTML."location.toString()."Use Ryushe's payload examples for shapes, but adapt them to the context.
Confirmed reflected XSS needs execution proof:
If browser tooling is unavailable, mark as Likely or Potential and record
the blocked proof step.
Include full URL, parameter/header/body field, reflected context, payload, mutation family, browser proof status, and stop reason.
documentation
Use when attacker-controlled input is saved and rendered later in a profile, comment, title, notification, admin view, export, email, feed, upload metadata, or other stored render surface.
data-ai
Use when inspecting proxy traffic from PwnFox-profiled browser sessions, filtering Caido/Burp/proxy history by X-PwnFox-Color, or interpreting user phrases like 'Red session' as a distinct browser/auth/profile lane.
tools
# LFI — Local File Inclusion Bypass ## What It Does Tests LFI bypass techniques: path traversal, null bytes, wrappers, log poisoning. Load `general-security-testing-policy`, `live-testing-policy`, and `injection-testing-policy` before live testing. For file/path sinks, absence of an immediate file read or response delta is not a stop reason by itself; use the policy to reason about path normalization, extension allowlists, wrappers, encoding, parser differences, and stack-specific proof ladder
tools
Use when XSS depends on browser-side sources and sinks such as URL/query/hash, router state, local/session storage, cookies, postMessage, DOM parsing, framework render paths, or client-side sanitizer behavior.