security

Analyze software security risks across authentication, authorization, and input validation.

14|7|Updated Dec 4, 2025
One-click install
npx skills add https://github.com/aj-geddes/unicorn-team --skill security-aj-geddes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/aj-geddes/unicorn-team/tree/main/skills/security
Command: npx skills add https://github.com/aj-geddes/unicorn-team --skill security-aj-geddes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a structured approach for developers to identify, reason about, and mitigate security risks during software development, reducing vulnerabilities before production.

Core Features & Use Cases

  • Threat modeling with defense-in-depth principles across authentication, authorization, and data handling.
  • OWASP Top 10 awareness and mapping to practical secure coding patterns.
  • Guidance for secure reviews and security tooling integration with audit logging and monitoring.

Quick Start

Review your feature with a threat-modeling mindset and implement defense-in-depth controls to mitigate common vulnerabilities.

Frequently Asked Questions about security

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

FAQPage Schema
How do I apply threat modeling to secure web services and APIs?

Threat modeling for web services and APIs involves analyzing authentication, authorization, and input validation processes to identify security risks. This structured approach helps fortify applications by mapping defense-in-depth controls before production deployment.

What is defense-in-depth in secure coding and when do I need it?

Defense-in-depth in secure coding is a strategy using multiple overlapping security controls to protect data and application layers. You need it during software development to reduce vulnerabilities across authentication, authorization, and input validation workflows.

How do I map OWASP Top 10 vulnerabilities to practical secure coding patterns?

Mapping OWASP Top 10 vulnerabilities to secure coding patterns requires analyzing common security risks like injection and broken authentication. It aligns threat awareness with practical implementation steps to mitigate vulnerabilities during code reviews.

Can I use this approach for security reviews of API authentication and authorization?

Yes, you can use this approach for security reviews of API authentication and authorization. It analyzes software security risks specifically during these workflows, ensuring proper input validation and alignment with audit logging requirements.

What's the best way to integrate audit logging and security tooling into my application?

The best way to integrate audit logging and security tooling is to align them with your threat modeling and secure coding practices. This provides continuous monitoring and auditing outputs that track security events across web services.