安全审计与加固。覆盖SAST/SCA/密钥扫描/STRIDE威胁建模/合规检查,按语言特定工具链识别漏洞并提供修复方案。Use when the user asks to check security, scan for vulnerabilities, audit code, or prepare for compliance.
Router for application and code security — scanning a repository or diff for vulnerabilities, reviewing auth, secrets, and injection risks, generating patches for findings, and running a security pass before shipping. Use when the user mentions a security scan, vulnerability audit, CVE, secrets in code, auth review, injection, XSS, SQL injection, SSRF, dependency risk, or asks to check whether their code is safe to ship.
Find secrets left lying around (2FA recovery codes, OAuth client secrets, certificates and keys in Downloads/Desktop/Documents) and credential files other users can read (~/.ssh keys, ~/.npmrc, adbkey). Never reads the files; only offers permission tightening. Use when user says: "check for exposed secrets", "security check my mac", "are my keys safe".
Find vulnerabilities in the current source of a whole repository or selected paths. This is the default single-pass audit. Use the diff skill for PR, commit, branch, or working-tree changes and the deep skill for an explicitly requested deep scan.
STRIDE + OWASP-based security audit with optional auto-fix. Scans code for vulnerabilities, categorizes by severity, and can iteratively fix findings using vc-autoresearch pattern.
1.1k5mo agoReviewMountCreate a free account to mount
Use for a standard, single-pass security audit of an entire repository or a scoped path, package, folder, or submodule with no diff to review. This is the default repository scan. Do not use for PR, commit, branch, or working-tree diffs, or for deep, multi-pass scans.
Entry point for the Adversis security plugin. Asks what you are trying to accomplish and routes you to the right skill: lint-baseline, threat-model, or security-persona. Start here.
Mandatory credential protection skill for all agents. Prevents reading, exposing, or leaking credentials, secrets, API keys, tokens, passwords, and auth-capable config files.
Security Auditor
Evaluate security implications of tools, configurations, plugins, and the intelligence hub itself.
## Input
`/security [target]`
Targets:
- No argument: full hub audit
- A tool name: evaluate that specific tool
Use when handling user input, authentication, authorisation, secrets, file uploads, or database queries. Also when adding a dependency, exposing an endpoint, or reviewing whether something is safe to ship.
Adversarial security gate. Reviews the change for vulnerabilities and tries to exploit them against a local environment. A confirmed exploit blocks the merge. Runs after merge-risk, before qa. Usage - /sous:security <change-id>
Audit security boundaries in AI, agent, RAG, and MCP systems, or manage project secrets with SOPS and age. Use for threat models, scoped security reviews, encrypted dotenv migration, recipient rotation, and secret exposure response.
Sécurité applicative, OWASP Top 10, gestion des secrets, authentification, et bonnes pratiques de sécurité. Use when reviewing code for vulnerabilities, applying OWASP Top 10, handling authentication or authorization, managing secrets and tokens, auditing dependencies, or when the user mentions securite, vulnerabilite, XSS, injection, CSRF ou mot de passe.
Assess what is built against the OWASP baseline: the dependency audit, secrets scan and Semgrep where installed, then a read-only reviewer through the OWASP checklist. Findings become bug items, people and process items go to the director, and a dated report goes in product/security/. Use for "run a security assessment", "check the app against OWASP", "is this secure", or when /next-task or /release calls for one.
Implement secure coding practices against common vulnerabilities. Use when handling user input, file paths, subprocess calls, SQL queries, API keys, or building web endpoints. Covers input validation, injection prevention, secret management, and XSS/CSRF protection across Python, TypeScript, Go, and Rust. Do NOT use for general error handling (use error-handling skill) or for remediating dependency vulnerability scanner failures and CVE / GHSA advisories (use cve-remediation skill).
Create security architecture diagrams using PlantUML syntax with identity, encryption, firewall, and compliance stencil icons. Best for IAM flows, zero-trust models, encryption pipelines, and threat detection architectures.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.