Apply threat modeling and boundary validation to new features.
npx skills add https://github.com/deandum/claude-resources --skill security-deandum
Please help me install this Agent Skill. Skill: security Source: https://github.com/deandum/claude-resources/tree/main/skills/core/security Command: npx skills add https://github.com/deandum/claude-resources --skill security-deandum
Security is a design discipline that ensures threat modeling, authn/authz planning, secrets management, input validation, and OWASP awareness guide feature design from the outset to prevent vulnerabilities.
Proactively model security for a new feature by identifying threat surfaces and defining boundary validation and authorization rules before coding.
High-intent search queries and answers about installing and using this skill.
Threat modeling for new features involves mapping callers, inputs, data touched, and potential risks before coding. This process proactively identifies threat surfaces, allowing you to define strict boundary validation and authorization rules early in the design phase.
The best way to enforce input validation at API boundaries is to apply strict schemas, canonicalization, and size limits directly at the interface. This boundary validation rejects unsafe inputs immediately before they can reach internal services or data persistence layers.
Designing authorization checks requires requiring explicit access-control decisions for every protected action. By integrating strict authz planning into your feature design, you ensure that authorization rules are enforced before any user input or external integration triggers sensitive operations.
You need secrets management to prevent embedding credentials directly in code or configuration files. Isolating secrets from code ensures sensitive data remains protected, reducing the risk of exposure during threat modeling and preventing unauthorized access to protected actions.
OWASP Top 10 alignment improves API endpoint security by applying critical vulnerability considerations to all new surfaces. It ensures your design-time security decisions address common risks like broken authentication, boundary validation failures, and improper authorization before deployment.
Yes, this security design process is applicable to any feature handling user input, authentication, or data persistence across both API endpoints and internal services. It enforces boundary validation and explicit authorization decisions for all external integration interactions.
mamu7211Decompose feature ideas into technical specifications through structured design interviews.
rsmdtDesign CI/CD pipelines for GitHub Actions and GitLab CI with deployment strategies.
ArianHobson333Automate open-source intelligence collection from code repositories with secret scanning.
abdusamaraieIdentify software security vulnerabilities through code review and threat modeling.
