agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/xss/SKILL.md

xss

Skill1 starsChanged 3 months agoMITView on GitHub

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

9 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use xxe, open-redirect and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • sunilgentyalaSkill

    xxe

    XML External Entity injection expert methodology. Covers classic XXE, blind OOB XXE, XXE via file upload, XXE to SSRF, and XXE in PDF/DOCX parsers.

    Also in 4 projects that use this

  • yaklangSkill

    open-redirect

    Open redirect playbook. Use when URL parameters, form actions, or JavaScript sinks control navigation targets and may redirect users to attacker-controlled destinations.

    Also in 4 projects that use this

  • langbyyiSkill

    deserialization

    Insecure deserialization playbook. Use when Java, PHP, or Python applications deserialize untrusted data via ObjectInputStream, unserialize, pickle, or similar mechanisms that may lead to RCE, file access, or privilege escalation.

    Also in 3 projects that use this

  • langbyyiSkill

    csrf

    CSRF testing playbook. Use when reviewing state-changing web flows, anti-CSRF defenses, SameSite behavior, JSON CSRF, login CSRF, and OAuth state handling.

    Also in 3 projects that use this

  • VercelSkill

    oauth

    Configure OAuth providers (Google, Apple, Microsoft, Facebook, GitHub, etc.) to work with portless local dev URLs. Use when setting up OAuth redirect URIs, fixing "redirect_uri_mismatch" or "invalid redirect" errors, configuring sign-in providers for local development, or when a provider rejects .localhost subdomains. Triggers include "OAuth not working with portless", "redirect URI mismatch", "Google/Apple/Microsoft sign-in fails locally", "configure OAuth for local dev", or any task involving OAuth callback URLs with portless domains.

    Also in 3 projects that use this

  • +1 more from langbyyi

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Start with reflected unless prior evidence points to a more specific workflow.

    line 16
  2. Very specific:

    Follow each workflow next mapping in skill.yaml after reviewing generated findings.

    line 17
  3. Distinctive:

    If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.

    line 18

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Xss

Overview

Cross-Site Scripting detection — reflected, stored, DOM, blind, CSP bypass, mXSS, and WAF bypass

This is a thin human-facing router. Use skill.yaml as the source of truth for exact commands, inputs, outputs, and workflow chaining.

Quick Reference

  • Skill: xss
  • Severity range: info, low, medium, high, critical
  • Required tools: curl, ffuf, dalfox, arjun, nuclei, python3, playwright, wafw00f
  • Expected input files: parameterized_urls.txt, all_urls.txt, js_files.txt
  • Scope check: confirm authorization before running intrusive or authenticated testing.

Workflow Selection

  • Start with reflected unless prior evidence points to a more specific workflow.
  • Follow each workflow next mapping in skill.yaml after reviewing generated findings.
  • If a workflow has no script reference, treat it as a manual or tool-native workflow and use the closest phase runbook when available.
  • Runbooks: use runbooks/ and select the closest phase runbook when workflow names do not map 1:1.

Available Workflows

WorkflowPurposeScript pathsPrimary outputsEvidence
reflectedDetect reflected XSS in parameterized URLs..claude/skills/xss/scripts/xss_reflected_probe.py$OUTDIR/xss/reflected/findings.jsonl$OUTDIR/xss/reflected/evidence/
domScan downloaded JavaScript for DOM XSS sources and sinks..claude/skills/xss/scripts/xss_dom_sink_scanner.py$OUTDIR/xss/dom/findings.jsonl$OUTDIR/xss/dom/evidence/
csp-analysisFetch and analyze the target page Content-Security-Policy..claude/skills/xss/scripts/csp_analyzer.py$OUTDIR/xss/csp/analysis.txt$OUTDIR/xss/csp/evidence/
context-encoderGenerate encoded variants for an operator-supplied XSS payload..claude/skills/xss/scripts/xss_context_encoder.py$OUTDIR/xss/encoder/payloads.txt$OUTDIR/xss/encoder/evidence/

Evidence Required

  • Save raw request and response data for each confirmed finding.
  • Include timestamps, affected target, exact workflow name, tool versions, and reproduction steps.
  • Store screenshots or terminal captures in the workflow evidence directory when the workflow defines one.
  • Evidence templates from skill.yaml:
  • xss_screenshot: Playwright screenshot showing alert/script execution
  • poc_html: HTML PoC page reproducing the XSS
  • dalfox_output: Dalfox automated XSS scanner findings

References

  • Source of truth: skill.yaml
  • Runbooks: runbooks/
  • OWASP WSTG: WSTG-CLNT-01, WSTG-CLNT-02

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.