Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/analyzing-security-headers

@820dfc8
Run it yourself

Analyze HTTP security headers of web domains to identify vulnerabilities and misconfigurations. Use when you need to audit website security headers, assess header compliance, or get security recommendations for web applications. Trigger with phrases like "analyze security headers", "check HTTP headers", "audit website security headers", or "evaluate CSP and HSTS configuration".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/analyzing-security-headers

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈102 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈1k more on demand in 6 files.

Description uses 5.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈409 characters, or 5.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Analyzing Security Headers

Overview

Evaluate HTTP response headers for web applications against OWASP Secure Headers Project recommendations and browser security baselines. Identify missing, misconfigured, or information-leaking headers across both HTTP and HTTPS responses.

Prerequisites

  • Target URL or domain name accessible over the network
  • Authorization to perform HTTP requests against the target domain
  • Network connectivity for both HTTP and HTTPS protocols
  • Optional: write access to ${CLAUDE_SKILL_DIR}/security-reports/ for persisting results

Instructions

  1. Accept the target domain. If only a domain name is provided, default to https://. For batch analysis, accept a newline-separated list.
  2. Fetch response headers using WebFetch for both HTTP and HTTPS endpoints. Record the full redirect chain and final destination URL.
  3. Evaluate critical headers -- flag any that are missing or misconfigured:
    • Strict-Transport-Security: require max-age>=31536000, includeSubDomains, and preload eligibility
    • Content-Security-Policy: check for unsafe-inline, unsafe-eval, overly broad default-src, and missing frame-ancestors
    • X-Frame-Options: require DENY or SAMEORIGIN
    • X-Content-Type-Options: require nosniff
    • Permissions-Policy: verify camera, microphone, geolocation restrictions
  4. Evaluate important headers -- report status and recommendations:
    • Referrer-Policy: recommend strict-origin-when-cross-origin or no-referrer
    • Cross-Origin-Embedder-Policy (COEP), Cross-Origin-Opener-Policy (COOP), Cross-Origin-Resource-Policy (CORP)
  5. Check for information disclosure -- flag Server, X-Powered-By, X-AspNet-Version, and any header revealing technology stack or version numbers.
  6. Inspect cookie attributes on Set-Cookie headers: verify Secure, HttpOnly, SameSite=Lax|Strict, and __Host-/__Secure- prefix usage.
  7. Calculate a security grade: A+ (95-100), A (85-94), B (75-84), C (65-74), D (50-64), F (<50) based on weighted presence and correctness of each header.
  8. Generate per-header remediation directives with configuration examples for Nginx, Apache, and Cloudflare.

See references/implementation.md for the five-phase implementation workflow.

Output

  • Headers Analysis Report: overall grade, per-header status (present/missing/misconfigured), and risk impact
  • Remediation Checklist: prioritized fixes with server configuration snippets
  • Cookie Security Assessment: attribute compliance for each Set-Cookie header
  • Comparison Table: side-by-side HTTP vs. HTTPS header differences

Error Handling

Error Cause Solution
Failed to connect to domain DNS resolution failure, firewall block, or domain down Verify domain spelling and DNS records; test alternate protocols
SSL certificate verification failed Expired, self-signed, or mismatched certificate Note TLS issue in report; indicates HSTS not properly enforced
Too many redirects Redirect loop between HTTP and HTTPS Report the redirect chain and analyze headers at each hop
HTTP 429 Too Many Requests Rate limiting by target server Implement backoff; queue domain for delayed re-analysis
Headers differ between HTTP and HTTPS Inconsistent server configuration Report both sets; highlight critical differences and flag HSTS gap

Examples

  • "Analyze security headers for https://tonsofskills.com and explain any CSP or HSTS issues."
  • "Check headers for example.com on both HTTP and HTTPS and provide an Nginx remediation config."
  • "Batch-analyze headers for five staging domains and rank them by security grade."

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings23d3 checks · Risk MEDIUM
  • Gen Agent Trust Hub23d

    The skill contains a significant mismatch between its stated purpose and its actual code implementation. While it claims to analyze HTTP security headers, the included analysis script is a generic directory size tool. Furthermore, the skill includes a utility that can dynamically generate shell scripts and grant them execution permissions, which poses a security risk if user-controlled data is included in the generated files.

  • Socket23d

    No alerts

  • Snyk23d

    Risk: MEDIUM · 1 issue

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last month
What it can do
Reads files Network
version
1.29.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
[
  "security",
  "compliance",
  "audit"
]
All 4 allowed tools
ReadWebFetchWebSearchGrep
Other metadata
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/analyzing-security-headers