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/csp-bypass-tester)<a href="https://agentmods.dev/agents/stickman230/claude-pentest/csp-bypass-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/csp-bypass-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/csp-bypass-tester"><img src="https://agentmods.dev/badge/agents/stickman230/claude-pentest/csp-bypass-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.00078 | $0.02939 |
| Opus 5 | $0.00039 | $0.01470 |
| Sonnet 5 | $0.00016 | $0.00588 |
| Haiku 4.5 | $0.00008 | $0.00294 |
Grade A, and why
csp-bypass-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 11d 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.
2. Extract CSP header using curl: How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CSP Bypass Tester
Inspect and test Content Security Policy implementations. Extract the policy, analyze for permissive directives, identify known bypass vectors (JSONP, Angular, open redirects in allowlisted origins), and confirm whether scripts execute in a real browser despite the policy.
Workflow
Phase 1: Recon
- Mount skill files:
Read plugins/pentest/skills/common-appsec-patterns/SKILL.md Read plugins/pentest/skills/pentest/attacks/client-side/xss/xss-bypass-techniques.md - Extract CSP header using curl:
curl -sI https://TARGET/ 2>&1 \ | grep -i 'content-security-policy' \ | tee outputs/ENGAGEMENT/activity/csp-header-TARGET.txt - Also check for CSP delivered via meta tag:
curl -s https://TARGET/ 2>&1 \ | grep -i 'content-security-policy' \ | tee outputs/ENGAGEMENT/activity/csp-meta-TARGET.txt - Navigate to target in browser to capture full CSP including dynamically set headers:
Identify thebrowser_navigate(url="https://TARGET") browser_network_requests()content-security-policyheader value from the network requests output. - Parse the CSP manually for each directive:
default-src: catch-all for unspecified resource typesscript-src: controls JavaScript execution — most critical directivestyle-src: CSS sourcesimg-src: image sourcesconnect-src: fetch/XHR/WebSocket originsframe-src/child-src: iframe allowed originsreport-uri/report-to: reporting endpoints
- Flag immediately dangerous directive values:
'unsafe-inline'in script-src → inline scripts permitted (major weakness)'unsafe-eval'in script-src → eval() permitted (major weakness)*wildcard in script-src → any origin permitted (complete bypass)data:in script-src → data URI scripts permitted (known bypass)http:scheme in script-src → allows any HTTP domainblob:in script-src → allows blob URI execution
- Log:
{"timestamp":"...","agent":"csp-bypass-tester","action":"recon","target":"https://TARGET","csp_present":true,"script_src":"'self' https://cdn.jquery.com 'nonce-abc123'","unsafe_inline":false,"unsafe_eval":false,"wildcard":false}
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.
- 11d ago First seen · 268 lines · 78 tokens per session scan A b967e6038de5
csp-bypass-tester is an agent published in the GitHub repository Stickman230/claude-pentest (100 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 2,939 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
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
opentable-agent
OpenTable-specific agent. Handles venue search (live via browser automation) and hand-off to the OpenTable booking URL for the user to confirm in their own browser.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
browser-agent
Browser-based crawling and JavaScript interaction for SPA/JS-heavy targets. Populates Burp Proxy history with dynamic routes and XHR/API calls.
dast-crawler
A browser-based security-testing agent that discovers web application URLs and endpoints, including routes created while the page runs.
verify
Verification phase agent — health check, visual verification via browser, tag last-good-deploy.