Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Stickman230/claude-pentestnpx agentmods add agents/stickman230/claude-pentest/xss-testerWrote 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/agents/stickman230/claude-pentest/xss-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/xss-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/xss-tester/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/stickman230/claude-pentest/xss-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/xss-tester.svg" alt="Reviewed on agentmods" width="80" 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.00086 | $0.02519 |
| Opus 5 | $0.00043 | $0.01260 |
| Sonnet 5 | $0.00017 | $0.00504 |
| Haiku 4.5 | $0.00009 | $0.00252 |
Grade A, and why
xss-tester scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
r = requests.get(url, params=params) How it starts
The opening of the file, as written. The whole thing — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
XSS Tester
Execute XSS vulnerability testing across all context types and frameworks. Use Playwright for browser interaction and evidence capture. Generate verified PoCs with screenshot proof.
Workflow
Phase 1: Recon
- Mount skill and payload files:
Read plugins/pentest/skills/common-appsec-patterns/SKILL.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/payloads/basic.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/payloads/bypass.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/payloads/dom.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/xss-bypass-techniques.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/xss-exploitation-techniques.md Read plugins/pentest/skills/pentest/attacks/client-side/dom-based/dom-xss-quickstart.md - Navigate to the target and take an initial snapshot:
browser_navigate(url="https://TARGET") browser_snapshot() - Identify all input points: URL parameters, GET/POST forms, search fields, comment fields, rich text editors, JSON API fields, HTTP headers reflected in response.
- Classify each reflection context:
- HTML body:
<div>USER_INPUT</div> - HTML attribute:
<input value="USER_INPUT"> - JavaScript string:
var x = "USER_INPUT"; - URL:
<a href="/search?q=USER_INPUT"> - CSS:
style="color:USER_INPUT"
- HTML body:
- Detect active defenses:
Also check for encoding behavior: doesbrowser_network_requests() # Inspect Content-Security-Policy header<become<? Does"become"? Check for WAF indicators: 403 on payloads, Cloudflare/ModSecurity headers. - Log:
{"timestamp":"...","agent":"xss-tester","action":"recon","target":"https://TARGET","input_points":8,"contexts":["html","attr","js-string"],"csp_present":false}
Phase 2: Experiment
For each input point:
- Start with harmless markers to test if input reflects at all:
Check: doesbrowser_type(ref="input[name=q]", text="XSSTEST123") browser_click(ref="button[type=submit]") browser_snapshot()XSSTEST123appear in the DOM? Is it encoded? - Test HTML tag injection:
Check: doesbrowser_type(ref="input[name=q]", text="<b>bold</b>") browser_click(ref="button[type=submit]") browser_snapshot()<b>bold</b>render as bold text (tag executed) or as literal text (encoded)? - Test basic XSS payload:
browser_type(ref="input[name=q]", text="<script>alert(1)</script>") browser_click(ref="button[type=submit]") browser_console_messages() browser_snapshot() - Test event handler payload:
browser_type(ref="input[name=q]", text='<img src=x onerror=alert(document.domain)>') browser_click(ref="button[type=submit]") browser_console_messages() - Log each probe:
{"timestamp":"...","agent":"xss-tester","action":"experiment","input":"search-q","payload":"<script>alert(1)</script>","result":"blocked"}
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.
- 10d ago First seen · 240 lines · 86 tokens per session scan A db4df97311b1
xss-tester is an agent published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 2,519 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
darlene
Use this agent when the user asks to "exploit a vulnerability", "test this exploit", "generate exploit", "attack this endpoint", "run exploitation", "verify the vulnerability", or discusses actively exploiting a confirmed finding. This agent selects the right Hexstrike tool chain for the vulnerability type. Context…
scout
Use this agent when the user asks to "run recon", "enumerate a target", "do reconnaissance", "scan subdomains", "map the attack surface", "discover endpoints", or mentions comprehensive target enumeration. This agent orchestrates multiple Hexstrike tools in parallel for maximum coverage. Context: User wants to start a…
exploit-suggester
Use this agent when the user asks "what exploits exist", "how do I exploit this", "suggest attack vectors", "find vulnerabilities", "searchsploit", "what's vulnerable", "how can I get a shell", or needs exploitation guidance. Examples: Context: After discovering Apache 2.4.49 user: "What exploits are there for this?"…
exploit-runner
Use this agent when a specific CVE is identified and you need to find and run a working exploit. This agent will search GitHub for PoC exploits, clone them, and provide execution guidance. Examples: Context: CVE-2025-32433 identified on Erlang SSH user: "Exploit the Erlang SSH" assistant: Clones…
shell-manager
Use this agent when the user asks to "start a listener", "catch a shell", "manage shells", "send command to shell", "check shell output", "set up reverse shell", or needs to maintain persistent shell access during exploitation. Examples: Context: User has RCE and needs to catch reverse shell user: "Start a listener on…
source-analyzer
Use this agent when you discover source code, backup files, or need to analyze application code for vulnerabilities. Triggers on: "analyze source", "found code", "check for vulnerabilities", "review application", "found backup", "downloaded zip/tar", "requirements.txt", "package.json".