More screenshots
Works with the AI Agents you already use
Content Security Policy Check
Each looks like protection in a review and gives none.
$5
Content Security Policy Check
Example session with this skill installed
Check this project with content-security-policy-check.
- Read your context and instructions
- Compiled the content security policy
- Generated the UI component
$ python3 scripts/check_csp.py examples/risky
BLOCK nginx/shop.conf:18 C03 FIXED_NONCE
add_header Content-Security-Policy "script-src 'nonce-2726c7f26c' 'strict-dynamic'; object-src 'none'" always;
Why: A nonce is written as a fixed value ('nonce-2726c7f26c') in a config file, meta tag or code string, so every response sends the same nonce. Anyone who reads one page can put that nonce on an injected script and it runs. CSP requires a new unguessable value each time the policy is sent.
Safer: Generate a random nonce of at least 128 bits for every response on the server (nginx $request_id, a middleware or a framework helper) and use it in both the header and the script tags, or use hashes ('sha256-...') for static pages.
BLOCK public/index.html:7 C02 POLICY_NOT_READ_AS_WRITTEN
BLOCK server.js:11 C02 POLICY_NOT_READ_AS_WRITTEN
BLOCK vercel.json:7 C01 SCRIPTS_FROM_ANY_HOST
REVIEW Caddyfile:3 C18 SCRIPTS_NOT_RESTRICTED
REVIEW nginx/shop.conf:10 C11 SCRIPT_UNSAFE_INLINE
REVIEW nginx/shop.conf:10 C15 NO_FRAME_ANCESTORS
REVIEW nginx/shop.conf:10 C17 BYPASS_PRONE_SCRIPT_HOST
REVIEW nginx/shop.conf:18 C14 BASE_URI_NOT_RESTRICTED
REVIEW nginx/shop.conf:18 C15 NO_FRAME_ANCESTORS
REVIEW public/_headers:5 C16 POLICY_PART_NOT_ENFORCED
REVIEW public/index.html:7 C12 SCRIPT_UNSAFE_EVAL
REVIEW public/index.html:7 C16 POLICY_PART_NOT_ENFORCED
REVIEW server.js:10 C17 BYPASS_PRONE_SCRIPT_HOST
REVIEW vercel.json:7 C13 OBJECT_SRC_NOT_RESTRICTED
REVIEW vercel.json:7 C19 MISSPELLED_KEYWORD
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 6 files, 6 with Content-Security-Policy content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
index.html
TSX · React component
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
About this skill
script-src 'self' https: lets an injected script load from any HTTPS server, default-src self without quotes allows only a host named "self", a nonce written into nginx.conf is the same for every visitor, and frame-ancestors in a meta tag is ignored. Each looks like protection in a review and gives none. This skill finds those and the other CSP mistakes below before you ship, and tells you how to fix each one.
Your agent runs a scanner on HTML pages and templates, nginx, Apache and Caddy configs, _headers files, vercel.json, firebase.json, staticwebapp.config.json, netlify.toml, IIS web.config, Next.js next.config and proxy or middleware files, helmet options, Django SECURE_CSP and django-csp settings, Spring Security policyDirectives, and CSP header strings in Python, PHP, Ruby, Go, Java and C# code. It reads each policy the way CSP Level 3 browsers do (a nonce or hash turns off 'unsafe-inline', 'strict-dynamic' turns off host lists, base-uri and frame-ancestors do not fall back to default-src), follows values through template literals, string concatenation and constants in the same file, reads Next.js development-only values as in production, knows helmet's defaults, and skips test files that assert on sample headers. The strict policy from web.dev and the nonce examples from the Next.js CSP guide are not flagged. It never runs your code and never fetches your site. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- C01: script sources that allow any host: *, https:, http:, data:, or a wildcard over a top-level domain (fine only with 'strict-dynamic' and a nonce or hash)
- C02: a policy the browser reads differently from what is written: keywords, nonces or hashes without single quotes, hosts in quotes, directive names with typos, underscores, camelCase or a colon, missing semicolons, commas between sources, a meta tag after the body tag
- C03: a fixed nonce written into a config file, meta tag or code string
REVIEW
- C11: 'unsafe-inline' for scripts without a nonce, hash or 'strict-dynamic'
- C12: 'unsafe-eval' for scripts
- C13: no object-src or default-src, or object-src open to any host
- C14: a nonce-based policy without base-uri, or base-uri open to any host
- C15: a header policy without frame-ancestors when the same file sets no X-Frame-Options
- C16: parts that are not enforced: only a Report-Only header, Report-Only, frame-ancestors, report-uri or sandbox in a meta tag, a directive written twice, removed directives such as plugin-types
- C17: script hosts that can be used to bypass a host list: JSONP and AngularJS hosts (also through wildcards such as *.googletagmanager.com), public package CDNs unless the source names one package or file (cdn.jsdelivr.net/npm/ allows every package), wildcards over shared hosting such as *.cloudfront.net
- C18: a policy that restricts images, styles or connections but not scripts
- C19: a misspelled keyword such as 'unsafe-inlne' or 'slef', which browsers ignore (the report names the keyword it is closest to)
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source for each rule
- A risky and a safe example site (nginx, HTML, _headers, vercel.json, Express with helmet, Caddyfile), and the real report the scanner produces on the risky one
Limits It reads each file on its own: headers sent by other files, a CDN, a proxy or the framework are not known, so a missing frame-ancestors can be reported when X-Frame-Options is set elsewhere. Policies built at run time (from environment variables, a database or helper functions), Rails' content_security_policy block, and SvelteKit or Astro CSP config are not read, and nginx include and map are not followed. Nonces are judged by how they are written, not by how the server makes them. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Static check of config and code text. Headers sent by other files, CDNs, proxies or frameworks are not known; policies built at run time, Rails, SvelteKit and Astro CSP config, and nginx include and map are not read. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example site includes a clearly fake fixed nonce for the scanner to find. Nothing in it is run.