security-hardening

Audit repositories for exploitable security risks and prioritize fixes.

154|9|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/swyxio/skills --skill security-hardening-swyxio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-hardening
Source: https://github.com/swyxio/skills/tree/main/security-hardening
Command: npx skills add https://github.com/swyxio/skills --skill security-hardening-swyxio

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manual security audits often miss critical exploitable vulnerabilities or waste time on low-priority theoretical issues, leaving production software at risk without clear remediation steps. This Skill delivers a structured, pragmatic approach to application security hardening that focuses on real-world risks and actionable fixes.

Core Features & Use Cases

  • Attack Surface Mapping: Systematically identifies all auth/session models, API routes, file upload/download flows, secret storage, dependency entrypoints, and network egress points across your repo.
  • Risk-Prioritized Remediation: Separates must-fix pre-release vulnerabilities from deferred accepted risks, preserving core product behavior unless a fix requires a necessary change.
  • Validated Hardening & Reporting: Adds targeted security tests for bypasses, input validation failures, and secret leakage, runs dependency audits for known CVEs, and documents all residual risk with severity and recommended next steps. Use Case: If you are preparing a web application for production launch, use this Skill to catch auth bypasses, SSRF flaws, exposed secrets, and vulnerable dependencies before go-live.

Quick Start

Use the security-hardening skill to audit this repository for exploitable application security risks, prioritize critical fixes, and document any remaining residual risk.

Frequently Asked Questions about security-hardening

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

FAQPage Schema
How do I audit my codebase for exploitable application security risks before a production launch?

To audit for application security risks before launch, map your attack surface, prioritize exploitable vulnerabilities like auth bypasses and SSRF, and document residual risk with targeted fix plans.

What is risk-prioritized remediation for web application security?

Risk-prioritized remediation separates must-fix pre-release vulnerabilities from deferred accepted risks, ensuring security hardening focuses on real-world exploitable threats rather than theoretical compliance checks.

How do I check my repository for secret leakage and vulnerable dependencies?

Check for secret leakage and vulnerable dependencies by running dependency CVE audits, identifying secret storage entrypoints, and adding targeted security tests to catch validation failures.

Can I fix CORS and CSRF misconfigurations without changing core product behavior?

Yes, you can fix CORS and CSRF misconfigurations while preserving core product behavior, unless a specific remediation explicitly requires a necessary change to the application's functional logic.

What is the best way to document residual security risk for engineering stakeholders?

The best way to document residual security risk is to provide a clear report detailing severity levels, recommended next steps, and justifications for accepted risks following a vulnerability audit.

When should I not rely solely on automated vulnerability audits for appsec?

Do not rely solely on automated vulnerability audits when theoretical compliance checks fail to capture real-world risks; manual pragmatic hardening is needed to catch bypass and failure cases.