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 agentmods add skills/woohyun212/security-skill/security-headersnpx skills add woohyun212/security-skill --skill security-headersgit clone --depth 1 https://github.com/woohyun212/security-skillWrote 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/woohyun212/security-skill/security-headers)<a href="https://agentmods.dev/skills/woohyun212/security-skill/security-headers"><img src="https://agentmods.dev/badge/skills/woohyun212/security-skill/security-headers.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01385 |
| Opus 5 | $0.00008 | $0.00692 |
| Sonnet 5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
security-headers scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- `curl` installed (included by default on most Linux/macOS systems) How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
Sends an HTTP request to the target URL, collects response headers, and checks for the presence and proper configuration of security-related headers. Classifies each header as present, missing, or misconfigured, and provides remediation recommendations for missing or improperly configured headers.
When to use
- During web application security assessments (initial reconnaissance phase)
- When running a pre-deployment security checklist
- During bug bounty or penetration testing to quickly identify header vulnerabilities
Prerequisites
curlinstalled (included by default on most Linux/macOS systems)- HTTP/HTTPS access to the target server
Inputs
| Variable | Description | Example |
|---|---|---|
TARGET_URL |
Target URL to check (including scheme) | https://example.com |
Workflow
Step 1: Collect response headers
TARGET_URL="https://example.com"
curl -s -I -L \
--max-time 10 \
--user-agent "SecurityHeadersCheck/1.0" \
"$TARGET_URL" 2>&1 | tee /tmp/headers_raw.txt
echo "=== Collected Headers ==="
cat /tmp/headers_raw.txt
Step 2: Check individual security headers
check_header() {
local name="$1"
local pattern="$2"
local value
value=$(grep -i "^${pattern}:" /tmp/headers_raw.txt | head -1)
if [ -z "$value" ]; then
echo "[MISSING] $name"
else
echo "[PRESENT] $value"
fi
}
echo ""
echo "=== Security Header Check Results ==="
check_header "X-Content-Type-Options" "x-content-type-options"
check_header "X-Frame-Options" "x-frame-options"
check_header "Strict-Transport-Security" "strict-transport-security"
check_header "Content-Security-Policy" "content-security-policy"
check_header "X-XSS-Protection" "x-xss-protection"
check_header "Referrer-Policy" "referrer-policy"
check_header "Permissions-Policy" "permissions-policy"
Step 3: Detect misconfigured headers
echo ""
echo "=== Misconfiguration Check ==="
# HSTS: warn if max-age is too short
hsts=$(grep -i "^strict-transport-security:" /tmp/headers_raw.txt | head -1)
if [ -n "$hsts" ]; then
max_age=$(echo "$hsts" | grep -oP 'max-age=\K[0-9]+')
if [ -n "$max_age" ] && [ "$max_age" -lt 31536000 ]; then
echo "[MISCONFIGURED] HSTS max-age=$max_age (recommended: 31536000 or higher)"
else
echo "[OK] HSTS max-age is sufficient"
fi
fi
# X-XSS-Protection: warn if not set to 1; mode=block
xxp=$(grep -i "^x-xss-protection:" /tmp/headers_raw.txt | head -1)
if [ -n "$xxp" ]; then
if echo "$xxp" | grep -qi "0"; then
echo "[MISCONFIGURED] X-XSS-Protection: disabled with value 0"
fi
fi
# X-Frame-Options: ALLOW-FROM is an outdated approach
xfo=$(grep -i "^x-frame-options:" /tmp/headers_raw.txt | head -1)
if [ -n "$xfo" ]; then
if echo "$xfo" | grep -qi "allow-from"; then
echo "[MISCONFIGURED] X-Frame-Options ALLOW-FROM is not supported by most browsers. Use CSP frame-ancestors instead."
fi
fi
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.
- 3d ago First seen · 155 lines · 16 tokens per session scan A a886a1ba1c1a
security-headers is a skill published in the GitHub repository woohyun212/security-skill (21 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 1,385 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…