security-headers-check
Skill13 starsChanged 19 days agoApache-2.0View on GitHub
Check HTTP security headers on any URL. Grades CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy. Produces an A-F report with specific missing or misconfigured headers. No signup.
In this repository35 other files it gives its agents.
- accessibility-checkSkill
- agentic-app-risk-reviewSkill
- api-security-scanSkill
- broken-link-scanSkill
- cold-load-waterfallSkill
- complexity-hotspotsSkill
- console-error-scanSkill
- cookie-privacy-scanSkill
- core-web-vitalsSkill
- dead-code-scanSkill
- dependency-auditSkill
- diff-risk-reviewSkill
- error-handling-auditSkill
- evidence-code-auditSkill
- exploited-vulnerability-watchSkill
- flaky-selector-scanSkill
- form-validation-scanSkill
- i18n-rtl-auditSkill
- iac-misconfig-scanSkill
- invisible-inkSkill
- license-compliance-scanSkill
- mixed-content-scanSkill
- mr-nullSkill
- page-weight-budgetSkill
- railway-exposure-auditSkill
- responsive-screenshotsSkill
- script-quality-reviewSkill
- scunthorpe-checkSkill
- secret-scanSkill
- security-advisory-triageSkill
- security-auditSkill
- seo-checkSkill
- test-quality-reviewSkill
- third-party-bloatSkill
- ui-ux-scanSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 3 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Check each header category below against the captured response headers
- Very specific: line 33
Should not contain unsafe-inline without a nonce or hash
- Very specific: line 34
Should not contain unsafe-eval
- Very specific: line 35
Should not use wildcard * in script-src or object-src
- Distinctive: line 38
Should be present on HTTPS sites
- Very specific: line 44
Should be DENY or SAMEORIGIN
- Distinctive: line 56
Should be present (formerly Feature-Policy)
- Very specific: line 57
Should restrict at minimum: camera, microphone, geolocation
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Security Headers Check
Grade the HTTP security headers of any website. No signup required.
Prerequisites
- Playwright MCP (comes with Claude Code)
Trigger
- "Check security headers on https://..."
- "Security headers scan mysite.com"
- "Is my site missing any security headers?"
Workflow
- Navigate to the URL using
mcp__playwright__browser_navigate - Capture network response headers using
mcp__playwright__browser_network_requests - Check each header category below against the captured response headers
Headers to Check
Content-Security-Policy (CSP)
- Should be present
- Should not contain
unsafe-inlinewithout a nonce or hash - Should not contain
unsafe-eval - Should not use wildcard
*inscript-srcorobject-src
Strict-Transport-Security (HSTS)
- Should be present on HTTPS sites
max-ageshould be ≥ 31536000 (1 year)- Should include
includeSubDomains preloadis a bonus
X-Frame-Options
- Should be
DENYorSAMEORIGIN - (Note: CSP
frame-ancestorssupersedes this; award credit if CSP has it)
X-Content-Type-Options
- Should be
nosniff
Referrer-Policy
- Should be present
- Recommended values:
strict-origin-when-cross-origin,no-referrer,same-origin - Penalize:
unsafe-url, missing entirely
Permissions-Policy
- Should be present (formerly Feature-Policy)
- Should restrict at minimum:
camera,microphone,geolocation
- Grade the site:
| Score | Grade | Meaning |
| 6/6 | A | All headers present and well-configured |
| 5/6 | B | One missing or weak header |
| 3-4/6 | C | Several gaps — moderate risk |
| 1-2/6 | D | Most headers missing |
| 0/6 | F | No security headers at all |
- Output:
## Security Headers Report: [URL]
**Grade: C** (3/6 headers configured correctly)
### Issues
1. [MISSING] Content-Security-Policy
No CSP found. XSS attacks are not mitigated at the header level.
2. [WEAK] Strict-Transport-Security
Found: max-age=3600
Issue: max-age too short (3600s). Minimum recommended: 31536000 (1 year)
Fix: Strict-Transport-Security: max-age=31536000; includeSubDomains
3. [MISSING] Permissions-Policy
No Permissions-Policy found. Browser features unrestricted.
### Passed
- X-Frame-Options: SAMEORIGIN ✓
- X-Content-Type-Options: nosniff ✓
- Referrer-Policy: strict-origin-when-cross-origin ✓
### Quick Fix (copy-paste for most servers)
Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
Permissions-Policy: camera=(), microphone=(), geolocation=()
**Want automated security regression tests?** Try QualityMax — qualitymax.ioDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

