Harden code at trust boundaries with explicit validation and secure defaults.
npx skills add https://github.com/helderberto/agent-skills --skill harden-helderberto
Please help me install this Agent Skill. Skill: harden Source: https://github.com/helderberto/agent-skills/tree/main/skills/harden Command: npx skills add https://github.com/helderberto/agent-skills --skill harden-helderberto
Harden code proactively against vulnerabilities at the boundary where untrusted input enters the system. Use when implementing auth, handling user input, storing or transmitting sensitive data, integrating external APIs, adding file uploads, or any code that crosses a trust boundary. Don't use for reactive secret scanning (use safe-repo) or dependency CVE checks (use deps-audit).
Apply this skill when implementing a new API endpoint to enforce boundary validation, secure defaults, and safe data handling.
High-intent search queries and answers about installing and using this skill.
Harden code at trust boundaries by enforcing explicit boundary validation, secure-by-default configurations, and safe data handling practices. This prevents untrusted input from causing injection and data leakage across authentication, data handling, and external API calls.
A trust boundary in secure coding is the point where untrusted input enters a system, such as user input fields, file uploads, or external API responses. Boundary validation is needed whenever code crosses this boundary to ensure only safe data is processed.
Securely handle user input and file uploads in a new API endpoint by applying always-on boundary validation and encoding. Configure secure defaults and safe data handling practices to proactively harden the system against vulnerabilities from user-provided data.
This approach does not handle reactive secret scanning or dependency CVE checks. It proactively hardens code at trust boundaries to prevent vulnerabilities from untrusted input, distinguishing it from dedicated secret scanning or dependency auditing tools.
The best way to implement secure authentication and external API integrations is to enforce strict boundary validation and secure handling of secrets. Apply secure-by-default configurations to proactively harden code against vulnerabilities at these critical entry points.
You should not use proactive code hardening for untrusted input when you need reactive secret scanning in existing repositories or dependency CVE checks. Code hardening is designed for implementing auth, handling data, and integrating APIs, not for auditing dependencies or scanning secrets.
vinitgirdharApply Django security configurations for authentication, CSRF, SQL injection, and XSS protection.
xu-xiangSecure Spring Boot services with authentication, authorization, and input validation.
JFrangelDetects and remediates security vulnerabilities in code, infrastructure, and architecture using OWASP and DevSecOps standards for pre-production environments.
sadie100Audit infrastructure, applications, and development processes for security vulnerabilities.
