Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Security
BT Panel Skill that lets AI agents use BT Panel capabilities to manage websites, files, databases, Docker, scheduled tasks, and server environments, handling daily operations such as status queries, troubleshooting, and security checks; supports automatic deployment of BT Panel and MCP servers, and integration with AI agents such as Claude Code, Codex, Cursor, and WorkBuddy. Use when users need to manage servers via AI, install BT Panel, or configure BT Panel MCP servers.
Use when sending local changes back to the project (an added journal profile, a fixed checklist item, an adapted skill) or reporting a false positive or bug. Finds what changed, scans it for patient data, shows every line and sends nothing until you confirm.
Audit multi-tenant data isolation — tenant model fit (shared rows vs schema vs database), missing or unenforced tenant scoping, the tenant_id-leading composite index/key requirement, and cross-tenant leak risk where queries or constraints omit the tenant boundary. Module M9. Feeds both the Design & Integrity (Seguridad) and Performance & Scale (Escala) scores.
A tool for detecting and exploiting arbitrary file download and local file inclusion (LFI) vulnerabilities. Use curl, ffuf, wget and similar tools to test file download vulnerabilities, supporting path traversal, wrapper protocol exploitation, and sensitive file reading. Use this skill when the user needs to test file download functionality, detect LFI vulnerabilities, or read sensitive files on a server.
Local File Inclusion (LFI) vulnerability detection and exploitation tool. Uses tools such as curl and ffuf to test for LFI vulnerabilities, supporting path traversal, PHP wrapper exploitation, log poisoning RCE, and sensitive file reads. Use this skill when the user needs to detect LFI vulnerabilities or exploit file inclusion flaws to read server files.
This skill should be used when the user asks to "test for directory traversal", "exploit path traversal vulnerabilities", "read arbitrary files through web applications", "find LFI vulnerabilities", or "access files outside web root". It provides comprehensive file path traversal attack and testing methodologies
Enforce safe Frida 17 MCP operations with strict phase gating. Use when attaching/spawning sessions, writing or loading scripts, applying Java/native hooks, troubleshooting instrumentation failures, or interpreting Frida MCP output. Require docs-first usage and run the mandatory workflow: Idea -> Scripting -> Execution -> Notes.
Use this skill when the user asks to “test for insecure direct object references,” “find IDOR vulnerabilities,” “exploit broken access control,” “enumerate user IDs or object references,” or “bypass authorization to access other users’ data.” It provides comprehensive guidance for detecting, exploiting, and remediating IDOR vulnerabilities in web applications.
Complete Next.js authentication system. PROACTIVELY activate for: (1) NextAuth.js (Auth.js) setup, (2) OAuth providers (GitHub, Google), (3) Credentials provider, (4) Session management (JWT/database), (5) Protected routes with middleware, (6) Role-based access control (RBAC), (7) Login/registration forms, (8) Authorization patterns, (9) Type augmentation for sessions. Provides: Auth.js configuration, middleware protection, session hooks, RBAC patterns, login forms. Ensures secure authentication with proper session handling.
Full health and security audit for Rails apps, the review a principal engineer would do. Runs rubycritic, Brakeman, bundler-audit and ruby_audit, triages every finding with the LLM as judge, brings an OWASP Top 10 arsenal of checks for what scanners miss, and returns one impact-ranked action plan. Use for a Rails project audit, a security and health check, "nuke on rails", or a deep review of a vibecoded Rails app.
PHP web source code NoSQL injection audit tool. Identifies user input reaching MongoDB/DocumentDB query construction, analyzes whether operator injection exists ($gt/$ne/$where, etc.), and outputs severity ratings, PoCs, and remediation advice (omission not allowed).
PHP web source code session and cookie security audit tool. Identifies session fixation, insecure cookie flags, JWT verification flaws, and remember-me login risks, and outputs severity ratings, PoCs, and remediation advice (omission not allowed).
Create or refine a Promptfoo redteam config and generate probes from target behavior, code, or OpenAPI evidence. Use for purpose, trust boundaries, plugins, strategies, and grading guidance. Use promptfoo-provider-setup for connection work and promptfoo-redteam-run for an existing scan.
Use this skill whenever the user asks for a security analysis, vulnerability assessment, security audit, or any form of Security Assessment Report (SAR) over a codebase, infrastructure, API, database, or system. Triggers include: "audit my code", "find security issues", "run a security check", "generate a SAR", "check for vulnerabilities", "is this code secure", or any request that involves evaluating the security posture of a project, repository, service, or infrastructure. For a single snippet or a quick "is this secure?" question, answer inline and offer a full SAR instead of running it. Do NOT use for generic coding tasks, code reviews focused on quality rather than security, or performance optimization unless a security angle is explicitly present.
Security architecture and threat modeling. OWASP Top 10 2025 analysis, OWASP Agentic AI Top 10 (ASI01-ASI10), AI/LLM security patterns, supply chain security, modern API authentication (OAuth 2.1, DPoP, Passkeys/WebAuthn), vulnerability assessment, and security review for code and infrastructure.
Define, review, or update SECURITY_MODEL.md files that tell security review tools a repository's threat model, trust boundaries, invariants, reportable finding classes, and exclusions. Use when asked to "write a security model", "threat model this repo for scanners", "define security review scope", "what counts as a vulnerability here", "update SECURITY_MODEL.md", "why did the scanner flag or miss this", or to check whether existing security guidance still matches the code. Not for running a security review or editing the SECURITY.md disclosure policy.
This skill should be used when the user asks to “search for exposed devices on the internet,” “perform Shodan reconnaissance,” “find vulnerable services using Shodan,” “scan IP ranges with Shodan,” or “discover IoT devices and open ports.” It provides comprehensive guidance for using Shodan's search engine, CLI, and API for penetration testing reconnaissance.
Write, review, or audit Cairo anonymizer (helper) contracts for stateless or atomic STRK20 private DeFi. Covers the privacy_invoke entry point, OpenNoteDeposit returns, the balance-delta idiom, and swap, Vesu lending, and escrow patterns. Use when a privacy_invoke helper is actually the selected route; persistent positions may instead use the canonical shadow-account route in strk20-wallet-api.
Build privacy wallets and key-holding backends with the Starknet Privacy SDK (@starkware-libs/starknet-privacy-sdk). Covers createPrivateTransfers wiring, register, deposit, transfer, withdraw, multi-op batches, shadow accounts (formerly private sub-accounts), note discovery, setup requirements, and proving configuration. Also use for debugging SDK submissions: provingBlockId, proofFacts, tip 0n, INVALID_NONCE, note maturity, fresh-account sequencing, and AddressMap lookups. If the app talks to the user's wallet instead of holding keys, use strk20-wallet-api. For concepts use strk20-privacy.
[Hyper] Use when working on TanStack Start projects and the task involves auth, sessions, cookies, CSRF, secrets, env exposure, server functions/routes, headers/CSP, webhooks, or security review/fixes. Triggers on protecting routes, hardening auth flows, preventing secret leaks, securing server boundaries, or reviewing HTTP/security behavior in a TanStack Start app.
Evidence-first pull request judge that reviews a PR and posts one consolidated GitHub review with inline comments via the gh CLI. Runs the repo's own deterministic checks first, researches current official docs before any claim about external libraries or APIs, then reviews correctness, security, structural quality (code judo, spaghetti growth, file-size limits), and AI slop including useless code comments. Every finding must carry evidence, every comment passes a deterministic noise gate before posting, and the verdict (APPROVE, COMMENT, REQUEST_CHANGES) is weighed by findings. Use when asked to review a PR, judge this PR, review this branch or diff before merge, run the-judge, "revise esse PR", "faca o code review", or "julgue esse PR". Do NOT use for reviewing prose or documents, fixing CI failures, resolving merge conflicts, writing the fix itself, or responding to review comments (use gh-address-comments).
Design and operate AI governance: principles, decision rights, risk tiers, lifecycle gates, fairness, transparency, privacy, security, compliance mapping, maturity and board reporting across SaaS, API, self-hosted and agentic systems. Use to admit, update or retire Agent Skills, MCP servers and A2A capabilities; approve an agent for production actions; or decide earned-autonomy promotion, reduction or revocation. Cover GxP, ALCOA+, data integrity, electronic records, assurance and QMS interfaces for life sciences. Do not use for legal interpretation (legal-strategy), data-platform mechanics (data-architect/data-engineering), security implementation (secure-software-engineering), skill package inspection (agent-skills), or executing runtime changes (agent-production-operations).
Design cloud network architectures with VPC patterns, subnet strategies, zero trust principles, and hybrid connectivity. Use when planning VPC topology, implementing multi-cloud networking, or establishing secure network segmentation for cloud workloads.
Scans a repo's GitHub Actions workflows for the ten critical CI/CD attack vectors — template injection, fork code executed with privileges (pwn requests), cache poisoning, impostor action SHAs, secrets dumps, GITHUB_ENV hijack, write-token untrusted triggers, credentials in caches/artifacts, unverified remote code execution (curl|bash and mutable fetch-and-run), and dependency install scripts running in a job that holds secrets — reports every finding with a plain-English attacker scenario, plus pass/fail config hygiene checks, and fixes selected findings via per-finding subagents. Deliberately NOT comprehensive — critical exploit-chain checks only (references/why-these-ten.md). Use when: the user asks to audit or review CI/CD or GitHub Actions security posture, "is my CI secure", "audit my CI security", or names ci-secure / /ci-secure. Do NOT trigger for: CI speed, cost, or wall-clock audits ("why is CI slow") — use ci-speedup; CI config best-practices grading ("grade my CI", "CI score") — use ci-score.
This skill should be used when the user asks to “test for XSS vulnerabilities”, “perform cross-site scripting attacks”, “identify HTML injection flaws”, “exploit client-side injection vulnerabilities”, “steal cookies via XSS”, or “bypass content security policies”. It provides comprehensive techniques for detecting, exploiting, and understanding XSS and HTML injection attack vectors in web applications
Use only when the user explicitly asks to fix and verify a validated or plausible security vulnerability. Do not use for ordinary bug fixes, correctness or design review findings, general validation, or full PR, commit, branch, patch, or repository scans.
Integrates Clerk authentication into React Native Expo apps using @clerk/clerk-expo. Covers ClerkProvider setup, secure token caching (expo-secure-store), Expo Router/React Navigation auth guards, custom sign-in/sign-up flows (email/password + email codes), SSO/OAuth (useSSO), Sign in with Apple (useSignInWithApple), biometrics (useLocalCredentials), offline support, and production deployment allowlisting. Use when the user mentions Clerk + Expo, @clerk/clerk-expo, Expo Router auth, SSO/OAuth redirects, or deploying Clerk in a mobile app.
Deterministic exploit execution and payload control from validated primitives. Use for exploit implementation, payload hardening, chaining confirmed weaknesses, post-exploitation proof, controlled impact demonstration, reliability notes, and rollback or containment planning.
PHP web archive extraction (Zip Slip / path traversal) auditing tool. Identifies how extraction entry names are joined with the target directory and whether the base dir constraint is missing, and outputs exploitability grading, an observable PoC and remediation advice (omission is not allowed).
PHP exploit chain / POP (property-oriented programming) chain aggregator. Links the various vulnerability reports already produced into an exploitable-chain narrative based on satisfied preconditions (without adding new evidence-point dictionaries).
Translate privacy principles and legal requirements into data-flow, lifecycle, acceptance, and verification artifacts. Map data classification, purpose, processing, access, retention, deletion, residency, and consent; define verifiable privacy acceptance criteria; and produce data-lifecycle records, retention/deletion verification plans, and privacy change reviews. Use when engineering privacy into a system, feature, or data flow — not for legal advice, jurisdiction-specific regulatory interpretation, or replacing security engineering or incident response.
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.