secure-headers

Configure and enforce secure HTTP headers for web applications.

2|1|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Agentient/vibekit --skill secure-headers-agentient
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secure-headers
Source: https://github.com/Agentient/vibekit/tree/main/plugins/security-tools/skills/secure-headers
Command: npx skills add https://github.com/Agentient/vibekit --skill secure-headers-agentient

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps configure and enforce secure HTTP headers (CSP, HSTS, X-Frame-Options, and related cookie protections) to reduce web app attack surfaces.

Core Features & Use Cases

  • CSP: define trusted sources and policies to mitigate XSS and data injection.
  • HSTS: enforce secure transport for all subsequent requests.
  • X-Frame-Options and X-Content-Type-Options: prevent clickjacking and content-type sniffing.
  • SameSite cookies: ensure cookies have appropriate SameSite attributes.
  • Use cases: apply headers in Next.js, Express, and other frameworks, for production deployments.

Quick Start

Apply the provided headers configuration to your web application to enable CSP, HSTS, and frame and content-type protections.

Frequently Asked Questions about secure-headers

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I configure secure HTTP headers like CSP and HSTS for a web app?

To configure secure HTTP headers, apply a static configuration snippet covering CSP, HSTS, X-Frame-Options, and X-Content-Type-Options to your web application. This enforces trusted sources, secure transport, and prevents clickjacking.

What is the best way to set Content-Security-Policy to mitigate XSS in Next.js?

Setting Content-Security-Policy (CSP) in Next.js involves defining trusted sources and policies within a static header configuration snippet. This mitigates XSS and data injection attacks by restricting resource loading to approved origins.

Can I use this secure headers setup for production deployments in Express?

Yes, you can use this setup for production deployments in Express. It provides a static header configuration snippet that applies secure defaults for CSP, HSTS, frame options, and SameSite cookie attributes to protect web applications.

Do I need to manually configure SameSite cookies when enforcing secure HTTP headers?

When enforcing secure HTTP headers, the configuration includes tuning SameSite cookie attributes to ensure appropriate protections. It upgrades to secure defaults, ensuring cookies have proper SameSite attributes without requiring separate manual configuration.

Why should I enforce HSTS and X-Frame-Options on my web application?

Enforcing HSTS and X-Frame-Options protects your web application by enforcing secure transport for all subsequent requests and preventing clickjacking attacks. These secure HTTP headers significantly reduce the web app attack surface.