About security-headers
A skill for auditing and configuring HTTP security headers in web applications. It helps developers identify framework-specific settings, compare existing headers with best practices, generate fixes, and validate the result.
Key features
- 01Detects the web framework
- 02Checks existing header settings
- 03Compares configuration with best practices
- 04Generates framework-specific fixes
- 05Validates configured headers
- 06Covers seven HTTP security headers
Use cases
- 01Audit security headers in a web application
- 02Find missing or weak header settings
- 03Generate a framework-specific configuration change
- 04Verify headers after applying a fix
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ fusengine/ claude-plugins --skill security-headersAfter installing, type/security-headersin Claude Code to confirm it loaded.
Details
From the project README
This skill audits and configures HTTP security headers for a web application:
Content-Security-Policy and Strict-Transport-Security (HIGH severity if missing),
X-Content-Type-Options and X-Frame-Options (MEDIUM), and Referrer-Policy,
Permissions-Policy, X-XSS-Protection (LOW).
It detects the framework (Next.js next.config.js headers/middleware.ts, Laravel SecurityHeaders middleware, Express helmet, Django SECURE_* settings), checks the current configuration against best practice, generates a framework-specific fix, and validates the headers are properly set.
Security Headers Skill
Overview
Audit and configure HTTP security headers for web applications.
Required Headers
| Header | Purpose | Severity if Missing |
|---|---|---|
| Content-Security-Policy | Prevent XSS/injection | HIGH |
| Strict-Transport-Security | Force HTTPS | HIGH |
| X-Content-Type-Options | Prevent MIME sniffing | MEDIUM |
| X-Frame-Options | Prevent clickjacking | MEDIUM |
| Referrer-Policy | Control referrer info | LOW |
| Permissions-Policy | Control browser features | LOW |
| X-XSS-Protection | Legacy XSS filter | LOW |
Workflow
- Detect framework (Next.js, Laravel, Express, etc.)
- Check current header configuration
- Compare against security best practices
- Generate framework-specific configuration
- Validate headers are properly set
Detection Points
| Framework | Config Location |
|---|---|
| Next.js | next.config.js headers, middleware.ts |
| Laravel | SecurityHeaders middleware |
| Express | helmet middleware |
| Django | SECURE_* settings |
References
Comments
Markdown supported