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.
npx skills add Quality-Max/free-qa-skills --skill security-headers-checkgit clone --depth 1 https://github.com/Quality-Max/free-qa-skillsWrote 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/skills/quality-max/free-qa-skills/security-headers-check)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/security-headers-check"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/security-headers-check/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/skills/quality-max/free-qa-skills/security-headers-check"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/security-headers-check.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.00059 | $0.00812 |
| Opus 5 | $0.00030 | $0.00406 |
| Sonnet 5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
security-headers-check scanned grade A with 0 findings 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 8d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.io
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.
- 8d ago First seen · 100 lines · 59 tokens per session scan A 9f84a019c408
security-headers-check is a skill published in the GitHub repository Quality-Max/free-qa-skills (10 stars, last pushed 15d ago), licensed Apache-2.0. It adds 59 tokens to every session and 812 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
performance
Optimize web performance for faster loading and better user experience. Use when asked to "speed up my site", "optimize performance", "reduce load time", "fix slow loading", "improve page speed", or "performance audit".
seo
Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".
core-web-vitals
Optimize Core Web Vitals (LCP, INP, CLS) for better page experience using field and lab evidence. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".
web-quality-audit
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing. Use when asked to "audit my site", "review web quality", "run lighthouse audit", "check page quality", or "optimize my website".