About security-headers
A skill that audits and configures HTTP security headers for web applications. It detects the framework, checks existing settings, generates a framework-specific fix, and validates the result.
Key features
- 01Detects web framework and settings
- 02Checks headers against security guidance
- 03Generates framework-specific configuration
- 04Validates configured headers
Use cases
- 01Auditing an application's HTTP headers
- 02Adding missing security headers
- 03Checking header configuration after a change
Install
Copy the command and run it in a terminal.
$
npx skills add https:/ / github.com/ fusengine/ agents --skill security-headersAfter installing, type/security-headersin Claude Code to confirm it loaded.
Bundled filesreferences/headers-reference.mdreferences/templates/headers-config.md
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