Works with the AI Agents you already use
Website Security Configuration Auditor
Audit website configurations, headers, and TLS settings to identify risks and generate remediation roadmaps.
$29.99
Website Security Configuration Auditor
Example session with this skill installed
Audit these HTTP response headers for production security gaps:
Server: nginx
Content-Type: text/html
Strict-Transport-Security: max-age=31536000
X-Frame-Options: SAMEORIGIN
- Read your context and instructions
- Compiled the website security configuration
The assessment of the supplied HTTP headers for the production environment is complete. I have identified three missing headers and one configuration improvement.
Website Security Configuration Audit
Assessment scope
- Website / domain: User-supplied
- Environment: Production
- Technology stack: Nginx
- Evidence sources: HTTP Response Headers
- Baseline: Defensive Best Practices
Findings Overview
| ID | Finding | Severity | Confidence | Affected component | Status |
|---|---|---|---|---|---|
| SEC-01 | Missing Content-Security-Policy | High | High | Response Headers | Open |
| SEC-02 | Missing X-Content-Type-Options | Medium | High | Response Headers | Open |
| SEC-03 | Missing Referrer-Policy | Low | High | Response Headers | Open |
| SEC-04 | HSTS Missing includeSubDomains | Low | High | TLS/Headers | Open |
Detailed Findings
SEC-01: Missing Content-Security-Policy (CSP)
- Severity: High | Confidence: High
- Observed: No CSP header present.
- Expected: A defined CSP to mitigate XSS and data injection attacks.
- Impact: Increases risk of unauthorized script execution in the user's browser context.
Remediation: Implement a Content-Security-Policy header. Start with a restrictive policy like default-src 'self';.
SEC-04: HSTS Missing includeSubDomains Directive
- Severity: Low | Confidence: High
- Observed:
Strict-Transport-Security: max-age=31536000 - Expected:
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload - Remediation: Update the Nginx configuration to include subdomains and the preload directive for better coverage.
Next steps
- Implement a
default-src 'self'CSP header in the Nginx configuration and monitor for breakage. - Add
X-Content-Type-Options: nosniffto prevent MIME-type sniffing. - Update the HSTS header to include the
includeSubDomainsdirective.
Connects securely to your tools. The creator never sees your data.
About this skill
Securing web applications requires more than just running a scanner. This skill analyzes configuration evidence to identify hardening gaps across headers, TLS, DNS, and server settings without the noise of generic automated tools.
What it does
- Analyze configuration reviews HTTP headers, TLS settings, DNS records, and server files for security weaknesses.
- Prioritize risks assigns severity and confidence ratings to findings based on potential business impact.
- Remediation planning generates actionable steps to move from an observed state to a secure baseline.
- Verification mapping defines the specific evidence needed to confirm a vulnerability has been closed.
- Compliance mapping compares current settings against organizational policies or defensive best practices.
How it works
- Define scope by providing authorized domains, environments, and specific security objectives.
- Supply evidence such as sanitized Nginx/Apache configs, HTTP response headers, or dependency inventories.
- Analyze controls across domains like session management, CORS policies, and platform hardening.
- Generate report including an executive summary, prioritized roadmap, and technical finding details.
Frameworks & tools
Works with evidence from Nginx, Apache, WordPress, and cloud-hosted stacks. Analyzes outputs from TLS scanners, dependency checkers, and web server configuration exports.
Why this beats prompting it yourself
Generic prompts often hallucinate vulnerabilities or miss context-specific risks like HSTS scope. This skill follows a structured auditing workflow that enforces evidence-based confidence ratings and redacts sensitive data automatically.
Use cases
- Auditing HTTP response headers for missing or weak CSP and HSTS policies.
- Reviewing web server configuration files for directory listing or verbose error exposure.
- Creating a remediation roadmap from raw security scan results.
- Verifying cookie attributes and session management settings against hardening standards.
Known limitations
Does not perform live scanning or exploitation. Requires user-supplied evidence or authorized tool access. Cannot verify fixes without updated evidence.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
No independent scanning or exploitation. Requires manual evidence input. Results depend on evidence freshness. Does not provide formal compliance certification.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 10 days ago
Permissions
No special permissions declared or detected