security-guidance

Apply OWASP ASVS-based security guidance to development tasks with inline citations.

141|14|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/OWASP/secure-agent-playbook --skill security-guidance-owasp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-guidance
Source: https://github.com/OWASP/secure-agent-playbook/tree/main/skills/security-guidance
Command: npx skills add https://github.com/OWASP/secure-agent-playbook --skill security-guidance-owasp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Security-focused guidance that ensures development decisions align with OWASP ASVS, reducing security gaps early in planning and coding.

Core Features & Use Cases

  • Inline ASVS reference mapping for tasks and code decisions.
  • Consistent security decision documentation with verifiable guidance.
  • Inline citations and explicit remediation notes to support code reviews.
  • Escalation prompts when ASVS guidance is unclear or conflicting.

Quick Start

Provide ASVS-aligned security guidance for the current development task.

Frequently Asked Questions about security-guidance

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

FAQPage Schema
How do I apply OWASP ASVS security guidance to software development tasks?

OWASP ASVS security guidance is applied to development tasks by enforcing Level 1 baselines, generating verifiable safe defaults, and mapping inline citations to ASVS references for secure implementation.

What is the best way to ensure secure design for user input and authentication modules?

Secure design for user input and authentication is achieved by applying ASVS-aligned risk assessment guidance, which delivers actionable remediation notes and explicit security decisions for these critical module types.

Can I use OWASP security guidance for both architecture planning and code review?

OWASP security guidance supports both architecture planning and code review by providing consistent security decision documentation and inline ASVS citations to verify implementation safety across development phases.

How do I handle conflicting or unclear OWASP ASVS guidance during secure implementation?

Conflicting or unclear OWASP ASVS guidance during secure implementation is managed through escalation prompts that trigger when ASVS references lack clarity, ensuring safe default decisions are maintained.

Does ASVS security guidance cover cryptography and network communication vulnerabilities?

ASVS security guidance covers cryptography and network communication by applying Level 1 baselines and inline citations to these modules, ensuring secure data persistence and network transmission practices.