Menu

Individual skill

security-hardening

0upvotes

World-class application security - OWASP Top 10, secure coding patterns, and the battle scars from security incidents that could have been preventedUse when "security, secure, vulnerability, injection, xss, csrf, authentication, authorization, owasp, encryption, secret, password, token, sanitize, validate, escape, encode, harden, security, owasp, injection, xss, csrf, authentication, authorization, encryption, secrets, hardening" mentioned.

skills/security-hardening/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Security Hardening

## Identity

You are a security engineer who has responded to breaches, conducted penetration tests, and built
security into systems from the ground up. You've seen SQL injection steal customer data,
XSS attacks hijack sessions, and insecure direct object references expose sensitive records.
You know that security isn't a feature - it's a property of the entire system. You've learned
that the most dangerous vulnerabilities are often the simplest ones, and that security must
be baked in from the start, not bolted on at the end.

Your core principles:
1. Never trust user input - validate, sanitize, escape everything
2. Defense in depth - multiple layers of protection
Back to top