Website security
Transport and HTTP-header security for a website — HTTPS/TLS, HSTS, Content Security Policy, X-Content-Type-Options, clickjacking protection, cookie attributes, and security.txt. Use when configuring server headers, TLS, cookies, or a disclosure policy.From its SKILL.md
npx -y skills add paulgrape/skill-auditor --skill website-securityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.7 KB, 343 tokens by cl100k_base, as published. Nobody here has run it
Website security
Headers, transport, and policies that keep visitors safe. Curated from the Website Specification — Security (CC BY 4.0).
Required
- Serve every page over HTTPS with TLS 1.2 or 1.3; redirect plain HTTP to HTTPS.
- Send HSTS:
Strict-Transport-Security: max-age=...; includeSubDomains. X-Content-Type-Options: nosniffon responses.- Clickjacking protection via CSP
frame-ancestors(X-Frame-Optionsas legacy fallback). - Cookies are
Secure,HttpOnlywhere possible, with an explicitSameSite; use__Host-/__Secure-prefixes.
Recommended
- Content Security Policy restricting script, style, image, and frame sources.
Referrer-Policy: strict-origin-when-cross-origin.Permissions-Policyto turn off unused powerful features (camera, mic, geolocation).- Subresource Integrity (SRI) hashes on third-party scripts and styles.
/.well-known/security.txttelling researchers how to report vulnerabilities.- DNS CAA records restricting which CAs may issue certificates.
Example headers
Strict-Transport-Security: max-age=63072000; includeSubDomains
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'self'; frame-ancestors 'none'
Referrer-Policy: strict-origin-when-cross-origin
Full item list and rationale: https://specification.website/checklist/
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most security skills give in 343 tokens
Counted across 648 of the 828 authors here whose files we hold, read 2026-08-07
- Parameterize all database queriesin 68 of 648, across 51 files
- Hash passwords using bcrypt, scrypt, or argon2in 49 of 648, across 36 files
- Apply rate limiting to authentication endpointsin 48 of 648, across 24 files
- Configure security headersin 35 of 648, across 19 files
- Validate all inputsin 32 of 648, across 24 files
- Validate all external input at the system boundaryin 29 of 648, across 19 files
- Run containers as a non-root userin 28 of 648, across 15 files
- Use httponly secure samesite cookies for sessionsin 26 of 648, across 15 files
- Run dependency audits before every releasein 21 of 648, across 10 files
- Encode output to prevent cross-site scriptingin 21 of 648, across 11 files
- Copy dependencies before source codein 20 of 648, across 9 files
- Store secrets in environment variablesin 20 of 648, across 18 files
Said here and by no other author read
- serve pages over HTTPS with TLS 1.2 or 1.3
- redirect plain HTTP to HTTPS
- send HSTS with includeSubDomains
- enable clickjacking protection via CSP frame-ancestors
- apply a restrictive Content Security Policy
- set Referrer-Policy to strict-origin-when-cross-origin
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.