Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API topic skill.
Fix a security vulnerability without leaking it before the release. Work happens on a local-only branch that is never pushed, then merges straight into the branch the release workflow publishes from. The fix becomes public at the same moment CI publishes the release, so the package keeps npm provenance. Use this skill whenever the user asks to fix a security issue, vulnerability, advisory, CVE or GHSA, or when other work finds one, even if they do not say "security-fix".
Configure DevExpress XAF security: roles, permissions, users, and background job authentication. Use when setting up role permissions in Updater.cs, implementing object-level security, exporting/importing roles, creating background job security contexts, or troubleshooting permission issues. Covers type-level vs object-level permissions, CurrentUserIdOperator, PermissionsReloadMode, and the role update caveat.
Security scanning, evaluation, audit, resolution and monitoring for Summit websites and apps. Runs secrets, dependency, static-analysis, CI-workflow, header/TLS and live-site checks; normalizes every result into one findings file; gates production deploys; then triages findings and fixes them one atomic PR at a time. Activates on "security scan", "security audit", "is this site secure", "check for secrets", "vulnerability scan", "harden this site", "fix security findings", "security gate", "pre-launch security check", or as the security part of the framework's audit, launch gate (SUMMIT-252) and monitor modes.
Use this skill to run a security scan combining SAST analysis, secret/credential detection, dependency vulnerability scanning (SCA), and container/IaC misconfiguration checks on staged code or the full codebase. Invoke as `/security-scan` to scan only git-staged files (fast, pre-commit use), or `/security-scan full` to scan the entire codebase. Uses semgrep or opengrep for SAST, trufflehog for secrets, and trivy (preferred) or grype for SCA and container/IaC scanning. Validates and deduplicates findings, generates a structured markdown report with severity ratings, and offers to auto-remediate fixable issues. Trigger this skill whenever the user wants to: run a security scan, check for secrets or credentials in code, scan dependencies for CVEs, check container or IaC configuration, do a SAST scan before committing, scan for vulnerabilities, run semgrep, trufflehog, trivy, or grype, or get a security report on their code.
This skill should be used when the user asks to \"run a security scan\", \"check for vulnerabilities\", \"security audit\", \"ship secure\", \"vibecheck scan\", or \"pre-deploy security check\". Runs 156 automated security checks across 15 categories and produces a categorized vulnerability report.
Security review skill for the vykar backup tool (Rust). Use when reviewing code for security issues, auditing cryptographic implementations, checking for credential leaks, reviewing unsafe code, or validating the security model of the backup tool. Covers encryption, key management, repository integrity, hook execution, config parsing, dependency auditing, and backup-specific attack surfaces.
Find and remove secrets, real hostnames, IPs, credentials, and private data from a repo before publishing. Use before any public release, screenshot commit, or README update.
2430d agoReviewMountCreate a free account to mount
Request a security expert assessment for code changes that touch child process spawning, file system access, configuration loading, or environment variable handling. Use when the Reviewer identifies security-sensitive changes in the MCP-LSP bridge.
Audit the game for security vulnerabilities: save tampering, cheat vectors, network exploits, data exposure, and input validation gaps. Produces a prioritised security report with remediation guidance. Run before any public release or multiplayer launch.
Security code review for Tauri/Rust/TypeScript desktop apps and Hono/oRPC APIs. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", or review code for injection, XSS, IPC abuse, path traversal, or authentication issues. Provides confidence-based reporting tuned to the Deadlock Mod Manager stack.
Move smart contract security on Sui. Use when reviewing Move code for security vulnerabilities, designing access control patterns, handling capabilities safely, securing randomness usage, validating invariants, planning upgrade governance, managing keys, or auditing privileged operations. Also use when the user asks about UpgradeCap security, capability revocation, shared object authorization, onchain randomness restrictions, oracle data validation, emergency controls, or frontend transaction signing safety.
2019d agoReviewMountCreate a free account to mount
Generate a complete SECURITY.md file for any software project. Use whenever the user asks to create, write, generate, or draft a SECURITY.md — a comprehensive security documentation covering threat models, security controls, authentication, authorization, data protection, compliance requirements, and security best practices.
Scan your OpenCode configuration (.opencode/ directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks AGENTS.md, settings.json, MCP servers, hooks, and agent definitions.
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.