Assess, route and report a suspected security vulnerability in Apache StreamPipes against the project's threat model. Use when a task involves a potential vulnerability, an exploit claim, a security finding from a scanner, or a decision about whether something is in or out of the security model.
7562mo agoReviewMountCreate a free account to mount
Add stateless JWT authentication to a Symfony API with LexikJWTAuthenticationBundle — firewall wiring in security.yaml, token TTL and refresh, and a custom authenticator when the defaults are not enough. Use when the user must configure a Symfony firewall for JWT — the login entry point, the api firewall, and the token authenticator in security.yaml; the user needs to authenticate a Symfony API statelessly with JWT tokens issued and verified by LexikJWTAuthenticationBundle; the user wants to set the JWT token TTL, add refresh tokens, or build a custom Symfony authenticator for token handling. Keywords: security, auth, authentication, jwt, symfony, firewall, stateless, api.
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.
Configure and manage Claude Code security protections for sensitive files, credentials, and data. Use when the user invokes /security-setup to set up or modify protections against unauthorized file access, credential exposure, or sensitive data leaks.
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.
2426d 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.
Plain text files in a repository that tell a coding agent how the project works: commands to run, conventions to follow and things to avoid. CLAUDE.md, AGENTS.md, cursor rules and skills are the common kinds.
CLAUDE.md or AGENTS.md?
CLAUDE.md is read by Claude Code. AGENTS.md is an open format that Codex, Cursor and other agents read. Many projects keep one and point the other at it.
What is a skill?
A folder with a SKILL.md that describes one capability, such as filling PDFs or reviewing code. The agent loads it only when the task calls for it.
Can I search my own team's files too?
Your agents already can, over MCP, limited to the files you're allowed to read. Searching them from this page is coming.