Browse Secure Claude Skills
Search verified agent skills and review security grades before installing · full A–Z index
- SecurityVulnerability scanning, encryption, and secure coding practices.Votes: 0GitHub stars: 2
- Security ArchitectureSystem-level security architecture: threat modeling, secure-by-design, defense-in-depth, zero-trust, trust boundaries, TEE/confidential computing, and secure boot / chain of trust. Architect-level — designing the security of a system, not app-level OWASP bug fixing. USE WHEN: designing a system's security architecture, "threat model", "zero-trust", "defense in depth", "trust boundary", "TEE", "enclave", "confidential computing", "secure boot", "attack surface", security design review. DO NO...Votes: 0GitHub stars: 31
- SecuritySecurity scanning, vulnerability assessment, and hardeningVotes: 0GitHub stars: 22
- Rule SecuritySecurity rules this project always applies: secret handling, input validation, parameterized queries, and Supabase RLS. Load before writing code that touches credentials, user input, queries, or auth.Votes: 0GitHub stars: 6
- SecurityAuto-apply security basics. Never ask user about security choices. Just do it.Votes: 0GitHub stars: 103
- SecurityThis document provides guidance on security best practicesVotes: 0GitHub stars: 6
- Security BoundariesUse when code executes commands, installs hooks/plugins, handles untrusted input, writes outside a workspace, or crosses privilege/network boundaries.Votes: 0GitHub stars: 5
- SecurityThreat modeling, compliance, and secure by design architectureVotes: 0GitHub stars: 5
- Security HardeningSecurity rules for authentication, authorization, RLS policies, CSP and headers, input validation and API routes. Use when building an auth flow, writing RLS policies, setting CSP or security headers, validating input, or auditing security.Votes: 0GitHub stars: 80
- Kit SecuritySecurity guardrails pack — injection, secrets, path traversal, auth defaults, deserialization, untrusted-content discipline. Use when asked for a security pass or when code touches user input, secrets, or auth.Votes: 0GitHub stars: 6
- Security ManagerUse when a task needs the judgment of a (physical/corporate) Security Manager — designing physical access controls, assessing a facility or event's security risk, responding to a security incident, or deciding how to allocate a security budget across prevention, detection, and response. Distinct from a cybersecurity/information-security role — this one covers physical and personnel security.Votes: 0GitHub stars: 15
- Security GuardBasic guardrails for agents. Injection checks, secret scanning, sandboxing.Votes: 0GitHub stars: 3
- SecuritySecurity best practices, OWASP Top 10, and secure coding guidelinesVotes: 0GitHub stars: 105
- SecSecurity Engineer for authentication, authorization, secrets, trust boundaries, unsafe inputs, data exposure, and practical security review.Votes: 0GitHub stars: 13
- Persona SecuritySecurity-first decision framework for threat modeling, vulnerability assessment, and compliance review. Use when user discusses security concerns, authentication design, encryption, OWASP compliance, XSS or CSRF prevention, or vulnerability remediation, or mentions 취약점, 보안, or 위협.Votes: 0GitHub stars: 3
- SecurityBuild-time security discipline — threat-model before controls, Always/Ask-First/Never boundary tiers, SSRF, supply chain, LLM/agent security, privacy. INVOKE PROACTIVELY when building anything touching auth, user data, uploads, outbound fetches, dependencies, or model output — even when nobody says "security". The after-the-fact review pass belongs to /security-review; validation mechanics: [[code-standards]]; infra secrets: [[infra-standards]].Votes: 0GitHub stars: 3
- Agent SecurityThreat-model and harden AI-agent trust boundaries, tools and data flows. Use when reviewing agent prompt injection, malicious retrieval/tool output, exfiltration, confused-deputy execution, tool poisoning or sandbox/credential boundaries. Do not use for general application security without a model/tool trust flow, or layering operational quality guardrails alone.Votes: 0GitHub stars: 2
- Senior Security../../../engineering-team/senior-security/SKILL.mdVotes: 0GitHub stars: 43
- Secure Software EngineeringUse when designing or implementing software securely: define security requirements, threat-model a feature, choose secure defaults, design authentication and authorization, handle untrusted data and secrets, evaluate dependencies, or review security-sensitive changes. Use for prevention during requirements, design, implementation, and review; not for post-build security assessments or scanning an existing codebase.Votes: 0GitHub stars: 36
- Security CheckIndependently assess a change, product, workflow, or deployment for realistic security and privacy risk, reporting outcome separately from coverage. Use for trust-boundary or exposure changes and explicit security review.Votes: 0GitHub stars: 5