Security Hardening
Audit or harden a defined application-security attack surface when the user explicitly requests a security audit, vulnerability investigation, or scoped security-hardening pass. Do not trigger for routine authentication changes, role design, scoped permissions, ordinary authorization bugs, dependency updates, generic production readiness, or feature implementation with incidental security implications.
Install
npx skills add swyxio/skills --skill security-hardeninggit clone --depth 1 https://github.com/swyxio/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/security-hardening ~/.claude/skills/security-hardeningPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Security Hardening Use this skill for pragmatic appsec work that produces prioritized fixes and residual-risk notes. Do not turn it into a compliance theater exercise. ## Counterweight: threat before control - Start with assets, trust boundaries, attacker capability, exposure, and plausible abuse paths. Do not apply the checklist uniformly. - Add or change a control only for a concrete reachable risk. Record when framework or provider defaults already cover it. - Prefer removing exposure, privilege, data, or code over adding middleware, policy layers, scanners, and monitoring. - Do not add rate limits, CORS/CSRF machinery, headers, runtime schemas, encryption, secret rotation, or dependency upgrades where the threat model does not require them. - Preserve one authorization source of truth; do not duplicate permission checks across artificial layers. - Avoid speculative findings based only on pattern matches. Confirm actual callers, deployment topology, and runtime behavior. - Keep fixes focused. Do not turn one vulnerability into a repo-wide security program, compliance project, dependency refresh, or release ceremony. - A scoped review may correctly conclude that no code change is needed. Report accepted and out-of-scope risk plainly. - Do not mutate production, rotate credentials, contact users, or change provider policy unless the active request explicitly authorizes it. ## Workflow 1. **Map the attack surface**
Details
- Skill name
security-hardening- Repository
- swyxio/skills
- Path
security-hardening/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Security Hardening skill do?
Audit or harden a defined application-security attack surface when the user explicitly requests a security audit, vulnerability investigation, or scoped security-hardening pass. Do not trigger for routine authentication changes, role design, scoped permissions, ordinary authorization bugs, dependency updates, generic production readiness, or feature implementation with incidental security implications.
How do I install the Security Hardening skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add swyxio/skills --skill security-hardening. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Security Hardening popular?
It lives in swyxio/skills, which has 201 GitHub stars and 12 forks.
Related skills
Accelevents API
201swyxio/skills
Use when reading or updating AI Engineer Europe speaker records through the Accelevents REST API, especially for full-record PUT updates, auth header quirks, and preserving existing speaker fields.
Accelevents Speaker Sync
201swyxio/skills
Use when website speaker, session, schedule, room, track, or headshot changes must be synchronized back to Accelevents for AI Engineer Europe 2026.
Agents SDK
201swyxio/skills
Build or debug stateful applications that specifically use Cloudflare's `agents` package, including Agent classes, routing, callable methods, synchronized state, scheduling, AIChatAgent, durable execution, or Agents SDK client hooks. Do not trigger for generic AI-agent design, the OpenAI Agents SDK, or ordinary Durable Object work that does not use the Cloudflare Agents SDK.
Security Scan
191jwynia/agent-skills
Scan code for security vulnerabilities including OWASP Top 10, secrets, and misconfigurations. Use when you need comprehensive security analysis of a codebase.
Secrets Scan
191jwynia/agent-skills
Detect API keys, passwords, tokens, and other secrets in code. Use when you need to find hardcoded credentials and sensitive data in source code.
Threat Model
228pproenca/dot-skills
Security threat modeling, attack surface mapping, and trust boundary analysis on a codebase. Triggers on 'threat model', 'security review', 'attack surface', 'trust boundaries', or when assessing a project's security posture. Also trigger when the user is about to build security-sensitive features (auth, crypto, file I/O, network services, native bridges) and needs to understand the threat landscape first — even if they don't explicitly say "threat model." Also triggers on 'what changed' or 'diff analysis' for incremental security review of recent commits.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.