Individual skill
web-csp-bypass
Get script to run despite a Content-Security-Policy — the step after finding an injection that CSP is blocking. Load when you have HTML/JS injection but the payload won't execute, on "CSP is blocking my XSS", or when auditing a CSP for weakness. Signals: a Content-Security-Policy header, a blocked-script console error, a reflected injection with no popup.
skills/web/web-csp-bypass/SKILL.md
Source commit ee0e0c50d2f6d941a14b73dd85a2b470d0ab976e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 27
- Repository last updated
- Oct 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-security Repository topic
- application-security Repository topic
- blue-team Repository topic
- bug-bounty Repository topic
- claude-code Repository topic
- codex Repository topic
- detection-engineering Repository topic
- gemini Repository topic
- writing Derived category
- security Derived category
- security-application Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 2,716 bytes
Read excerpt
# Bypassing Content-Security-Policy
## When it applies
You have an injection point but CSP is stopping execution. CSP is a mitigation, not a fix — a weak
policy still lets script run, and turning a "blocked" XSS into a firing one is what makes the bug
real (and higher severity).
## Why it works
Most deployed CSPs have a gap: an over-broad allowlist, a leftover `unsafe-inline`, a reusable
nonce, a `script-src` host that also serves a JSONP/AngularJS gadget, or a missing `base-uri`/
`object-src`. Each gap is a path to execution the policy author didn't intend.
## Method
1. **Read the policy**: paste it into Google's CSP Evaluator; note `script-src`, `object-src`,