security

Enforce secure coding practices for agent-native apps with Zod schemas.

3|Updated Jun 10, 2026

Search Tags:#security #xss #input-validation #sql-injection #ssrf #coding-practices #secret-management

Ready to run

npx skills add https://github.com/BuilderIO/builder-agent-native-starter --skill security-builderio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security
Source: https://github.com/BuilderIO/builder-agent-native-starter/tree/main/.agents/skills/security
Command: npx skills add https://github.com/BuilderIO/builder-agent-native-starter --skill security-builderio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Secure coding practices prevent data leaks, insecure inputs, and credential exposure in agent-native apps by enforcing safe patterns and guardrails.

Core Features & Use Cases

Enforces input validation, secret handling, data scoping, and defense against SQL injection, XSS, SSRF, and credential leakage across actions, routes, and components.
Provides guidelines to prevent data leakage and insecure deployments; includes examples for Zod schemas, safe credential storage, and guarded fetch patterns.
Use Case: When writing an action that processes user data, apply these rules to ensure validation and safe data access, preventing data breaches and insecure deployments.

Quick Start

Have developers apply defineAction with a Zod schema and use the framework's security primitives before handling user data.

Frequently Asked Questions about security

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

FAQPage Schema

How do I prevent SQL injection and XSS in agent-native apps?▼

To prevent SQL injection and XSS in agent-native apps, enforce strict input validation using defineAction with Zod schemas. This ensures user data is safely sanitized and scoped across action, route, and component layers before processing.

What is the best way to handle secret management and prevent credential leakage?▼

The best way to handle secret management and prevent credential leakage is using proper credential storage and the framework's security primitives. Guarding fetch patterns and safe data scoping isolate credentials from exposure across app layers.

How does Zod schema validation secure user data processing?▼

Zod schema validation secures user data processing by enforcing strict input boundaries within defineAction. This mechanism validates incoming data types and structures, preventing insecure inputs and data breaches before the application logic executes.

Can I use these secure coding practices for existing routes and components?▼

Yes, you can apply these secure coding practices to existing routes and components. The guidelines enforce data isolation and defense against SSRF across your app's action, route, and component layers, ensuring safe data access and preventing insecure deployments.

When do I need guarded fetch patterns to prevent SSRF?▼

You need guarded fetch patterns to prevent SSRF whenever your application makes external network requests based on user input. Applying these security primitives restricts unauthorized server-side resource access and protects against data leakage.