Individual skill
owasp-security
Apply OWASP frameworks (Top 10, ASVS, SAMM, MASVS, Cheat Sheets) to design, test, and harden web and mobile applications.
skills/owasp-security/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 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)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- design Derived category
- security Derived category
- testing Derived category
- security-application Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 7,496 bytes
Read excerpt
## Overview
OWASP (Open Worldwide Application Security Project) publishes community standards that are the common language of application security. The **OWASP Top 10** catalogs the most critical web-app risks; **ASVS** (Application Security Verification Standard) gives testable requirements at three assurance levels; **SAMM** (Software Assurance Maturity Model) guides program maturity; **MASVS** covers mobile; and the **Cheat Sheet Series** gives concise defensive implementation guidance.
This skill is how you turn those documents into practice: threat-driven secure design, checklist-based code review, and measurable verification. Everything here is defensive — the goal is building software that withstands attacks, not producing attacks.
Start with the project's risk profile, not the document set: a public-facing payment API needs ASVS Level 2 verified end to end, while an internal dashboard may live at Level 1 with selected Level 2 controls. The documents are a menu driven by risk, and the cheat sheets are the recipes your developers will actually open during implementation.
## When to use
- Starting a new web/API/mobile project and you need the baseline security requirements.
- Reviewing code or architecture for injection, auth, crypto, and misconfiguration issues.
- Defining security acceptance criteria for a release ("ASVS Level 2 verified").
- Responding to a pentest or bug-bounty report and mapping findings to remediations.