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.
git clone --depth 1 https://github.com/Stickman230/claude-pentestWrote 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/prototype-pollution-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/prototype-pollution-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/prototype-pollution-tester.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.00060 | $0.02453 |
| Opus 5 | $0.00030 | $0.01226 |
| Sonnet 5 | $0.00012 | $0.00491 |
| Haiku 4.5 | $0.00006 | $0.00245 |
Grade A, and why
prototype-pollution-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 8d 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.
curl -s -X POST https://TARGET/api/search \ How it starts
The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prototype Pollution Tester
Test for client-side JavaScript prototype pollution. Inject __proto__ and constructor.prototype
payloads into URL query parameters, hash fragments, and JSON request bodies. Confirm pollution
by evaluating Object.prototype in the browser DOM. Capture screenshot evidence on confirmed findings.
Workflow
Phase 1: Recon
- Mount skill files:
Read plugins/pentest/skills/common-appsec-patterns/SKILL.md Read plugins/pentest/skills/pentest/attacks/client-side/prototype-pollution/prototype-pollution-quickstart.md Read plugins/pentest/skills/pentest/attacks/client-side/prototype-pollution/payloads/basic.md - Navigate to the target and snapshot:
browser_navigate(url="https://TARGET") browser_snapshot() - Inspect loaded JavaScript libraries to identify pollution-vulnerable patterns:
Look for: lodash, jQuery, Backbone, Ember, Handlebars, jQuery deparam, qs library. These libraries are historically vulnerable to prototype pollution via object merging functions.browser_network_requests() - Check page source for client-side routing using URL parameters or hash fragments:
browser_evaluate(function="() => window.location.href") browser_evaluate(function="() => Object.keys(window).filter(k => k.includes('router') || k.includes('Router'))") - Identify JSON endpoints that accept arbitrary nested objects (search POST, filter, config):
cat outputs/ENGAGEMENT/inventory/api-endpoints.json 2>/dev/null | \ grep -i '"POST"\|"PUT"' | head -30 - Log:
{"timestamp":"...","agent":"prototype-pollution-tester","action":"recon","target":"https://TARGET","js_libraries":["lodash/4.17.20","jquery/3.5.1"],"hash_routing":false,"json_endpoints":["POST /api/config","POST /api/search"]}
Phase 2: Experiment
Test 1 — URL query parameter injection (__proto__):
browser_navigate(url="https://TARGET/?__proto__[testkey]=polluted")
browser_evaluate(function="() => Object.prototype.testkey")
If evaluate returns "polluted" → VULNERABLE via query parameter.
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.
- 8d ago First seen · 233 lines · 60 tokens per session scan A 9f5d1d538a63
prototype-pollution-tester is an agent published in the GitHub repository Stickman230/claude-pentest (99 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 2,453 once invoked, about $0.0003 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…
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
verification-runner
Run project-aware verification loop. Reads mix.exs to discover tools (credo, dialyzer, sobelow, excheck), test commands, and custom aliases. Use proactively after code changes.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.