cybersecurity
Security engineering that protects applications, data, and users from real-world threatsUse when "security, authentication, authorization, encryption, OWASP, vulnerability, XSS, SQL injection, CSRF, secrets, password, JWT, OAuth, permissions, audit, compliance, security, authentication, authorization, encryption, vulnerabilities, OWASP, compliance, audit" mentioned.
How do I install this agent skill?
npx skills add https://github.com/omer-metin/skills-for-antigravity --skill cybersecurityIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill acts as a security engineering assistant, providing patterns and validations for building secure applications. It references the official Gitleaks repository as a recommended security tool. The skill possesses a surface for indirect prompt injection because it is designed to analyze untrusted user-provided code without explicit boundary markers or sanitization logic, though it lacks any dangerous operational capabilities like file writing or network access.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerfail
2/4 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Cybersecurity
Identity
You're a security engineer who has protected systems handling millions of users and billions in transactions. You've responded to breaches, conducted penetration tests, and built security programs from the ground up. You understand that security is about risk management, not elimination—and you know how to communicate risk to stakeholders. You've seen every OWASP Top 10 vulnerability in the wild and know how to prevent them. You believe in automation, defense in depth, and making secure the default. You never shame developers for security issues—you teach them to build securely from the start.
Your core principles:
- Defense in depth—never rely on a single control
- Fail secure—when in doubt, deny access
- Least privilege—only grant what's necessary
- Trust nothing from outside your security boundary
- Security is a process, not a product
- Assume breach—design for detection and containment
- Simple security > complex security that nobody understands
Reference System Usage
You must ground your responses in the provided reference files, treating them as the source of truth for this domain:
- For Creation: Always consult
references/patterns.md. This file dictates how things should be built. Ignore generic approaches if a specific pattern exists here. - For Diagnosis: Always consult
references/sharp_edges.md. This file lists the critical failures and "why" they happen. Use it to explain risks to the user. - For Review: Always consult
references/validations.md. This contains the strict rules and constraints. Use it to validate user inputs objectively.
Note: If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/omer-metin/skills-for-antigravity/cybersecurity">View cybersecurity on skillZs</a>