Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/crazymarky/pentest-skills/exploit-xssnpx skills add crazyMarky/pentest-skills --skill exploit-xssgit clone --depth 1 https://github.com/crazyMarky/pentest-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/crazymarky/pentest-skills/exploit-xss)<a href="https://agentmods.dev/skills/crazymarky/pentest-skills/exploit-xss"><img src="https://agentmods.dev/badge/skills/crazymarky/pentest-skills/exploit-xss.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00071 | $0.05576 |
| Opus 5 | $0.00036 | $0.02788 |
| Sonnet 5 | $0.00014 | $0.01115 |
| Haiku 4.5 | $0.00007 | $0.00558 |
Grade A, and why
exploit-xss scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 731 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cross-Site Scripting (XSS) Detection Skill
⚠️ DANGER - Authorization Required
This skill is for AUTHORIZED SECURITY TESTING ONLY.
You must have:
- Written permission from the target system owner
- Legal authorization to test the target
- A defined scope of testing
Unauthorized XSS testing is ILLEGAL and unethical.
Prerequisites
Required Tools
# XSStrike - Advanced XSS scanner with DOM support
pip install xsstrike
# Or: git clone https://github.com/s0md3v/XSStrike
# Dalfox - Fast XSS scanner with pipeline mode
go install github.com/hahwul/dalfox/v2@latest
# XSpear - XSS testing with WAF bypass
gem install xspear
Python Requirements
# Install required Python packages for built-in scripts
pip install requests beautifulsoup4
# Optional: WebSocket XSS testing
pip install websockets
Optional Tools
# Burp Suite for manual testing
# OWASP ZAP for automated scanning
Quick Start
Basic URL Testing
# Test a URL parameter for XSS
python xsstrike.py -u "https://target.com/search?q=test"
# Fast scanning with Dalfox
dalfox url "https://target.com/search?q=test"
POST Request Testing
# Save POST request to file
dalfox file request.txt
# Or use XSStrike
python xsstrike.py -r request.txt
DOM XSS Testing
# DOM XSS with XSStrike
python xsstrike.py -u "https://target.com/page#test" --dom
# DOM XSS with Dalfox
dalfox url "https://target.com/page#test" --dom
Common Scenarios
1. Basic Parameter Testing (Reflected XSS)
Test URL parameters for reflection and injection:
# Single URL testing
python xsstrike.py -u "https://target.com/search?q=test"
# Dalfox for faster scanning
dalfox url "https://target.com/search?q=test"
# Specify parameter
dalfox url "https://target.com/search" -p q
What to check:
- Does the input reflect in the HTML response?
- What is the context (HTML tag, attribute, JavaScript)?
- Are there any filters/encoding applied?
What ships with it
40 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/attribute_xss_payloads.txt 912 B
- assets/blind_xss_payloads.txt 1.9 KB
- assets/common_xss_payloads.txt 706 B
- assets/csp_bypass_payloads.txt 21 KB
- assets/dom_xss_payloads.txt 887 B
- assets/framework_xss_payloads.txt 4.9 KB
- assets/modern_browser_xss_payloads.txt 16 KB
- assets/mutation_xss_payloads.txt 8.9 KB
- assets/mxss_payloads.txt 6.6 KB
- assets/polyglot_xss_payloads.txt 8.5 KB
- assets/svg_xss_payloads.txt 15 KB
- assets/waf_bypass_payloads.txt 3.0 KB
- assets/websocket_xss_payloads.txt 4.6 KB
- assets/xss_context_patterns.txt 2.1 KB
- references/csp_bypass_guide.md 8.2 KB
- references/dalfox_guide.md 4.9 KB
- references/dom_xss_guide.md 7.9 KB
- references/framework_xss_guide.md 9.7 KB
- references/mutation_xss_guide.md 9.6 KB
- references/svg_xss_guide.md 8.9 KB
- references/websocket_xss_guide.md 12 KB
- references/xspear_guide.md 5.9 KB
- references/xss_payload_techniques.md 9.1 KB
- references/xsstrike_guide.md 6.0 KB
- scripts/__pycache__/csp_detector.cpython-314.pyc 22 KB
- scripts/__pycache__/framework_xss_tester.cpython-314.pyc 21 KB
- scripts/__pycache__/svg_xss_tester.cpython-314.pyc 20 KB
- scripts/__pycache__/xss_context_analyzer.cpython-314.pyc 16 KB
- scripts/blind_xss_tester.py 15 KB runs code
- scripts/csp_detector.py 18 KB runs code
- scripts/framework_xss_tester.py 16 KB runs code
- scripts/mutation_xss_tester.py 17 KB runs code
- scripts/mxss_detector.py 18 KB runs code
- scripts/svg_xss_tester.py 15 KB runs code
- scripts/websocket_xss_tester.py 18 KB runs code
- scripts/xss_context_analyzer.py 13 KB runs code
- scripts/xss_full_scan.py 17 KB runs code
- scripts/xss_payload_generator.py 7.7 KB runs code
- scripts/xss_storage.py 3.6 KB runs code
- scripts/xss_tester.py 14 KB runs code
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 6d ago First seen · 731 lines · 71 tokens per session scan A 6304f9a63ac0
exploit-xss is a skill published in the GitHub repository crazyMarky/pentest-skills (303 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 5,576 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pentest-outbound-interaction-oob-detection
Outbound interaction and OOB validation for SSRF callbacks, blind XSS beacons, webhook abuse, XXE/OOB behavior, DNS/HTTP/HTTPS callback correlation, asynchronous server-side interaction proof, and egress validation.
intuitive-tests
Use this skill whenever the user asks about unit test best practices, test organization, flat test suites, redundant tests, test refactors, pytest/JUnit/Jest/xUnit layout, test taxonomy, flaky tests, coverage quality, fixtures, mocks, parametrization, pruning existing UTs, or "which tests are worth keeping." It…
browser-automation
Browser automation powers web testing, scraping, and AI agent interactions. The difference between a flaky script and a reliable system comes down to understanding selectors, waiting strategies, and anti-detection patterns. This skill covers Playwright (recommended) and Puppeteer, with patterns for testing, scraping…
ox-attest-goal
Pursue a customer capability to proven, Attest-backed BDD: author it from the customer's journey, drive the acceptance run to green, then hand to ox-attest-create to mint the honest red/green proof. Use when a user asks to add, improve, prove, or review a BDD/customer capability, or mentions customer flow, acceptance…
ox-attest-create
Turn a demonstrated red/green Attest run pair into an honest portable proof. Use when a user asks to attest, prove, stamp, record, publish, or explain a BDD capability's evidence. Inspect ox attest proof and the run artifacts first; use ox attest record only after a real red failure and a green recovery demonstrate…
visual-verification
Use for any UI/web project — make the verify gate cover more than unit tests by composing a pipeline (types → unit → design-scan → flow-smoke) and running the built-in yoke flow-smoke gate (landmark + zero console errors + screenshot proof to .yoke/proof/ /, video kept on failure). Catches the unwired-page /…