Skills
96,981 packaged capabilities and playbooks for agents. Install any of them with one command.
Security
Security intelligence for code analysis. Detects SQL injection, XSS, CSRF, authentication issues, crypto failures, and more. Actions: scan, analyze, fix, audit, check, review, secure, validate, sanitize, protect. Languages: JavaScript, TypeScript, Python, PHP, Java, Go, Ruby. Frameworks: Express, Django, Flask, Laravel, Spring, Rails. Vulnerabilities: SQL injection, XSS, CSRF, authentication bypass, authorization issues, command injection, path traversal, insecure deserialization, weak crypto, sensitive data exposure. Topics: input validation, output encoding, parameterized queries, password hashing, session management, CORS, CSP, security headers, rate limiting, dependency scanning.
Use when working with Gravity SMTP: installing, configuring, or troubleshooting WordPress transactional email delivery via SendGrid, Mailgun, Postmark, Brevo, SES, or custom SMTP. Critical: always verify version ≥ 2.1.5 to protect against CVE-2026-4020 which leaks API keys via unauthenticated REST endpoint.
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
Create, edit, and wire up agenix-encrypted secrets in this dotfiles repo. Use when adding API keys, tokens, credentials, passwords, or any sensitive values to NixOS host configs. Trigger phrases: "add a secret", "encrypt with agenix", "new age secret", "hide this value", "agenix secret".
A security testing methodology for AI Agent systems. Triggers when the target system uses AI Agents for tool invocation, multi-agent collaboration, or autonomous decision-making. Covers the OWASP Agentic AI Security Top 10 (ASI01-ASI10): goal hijacking, tool misuse, identity and privileges, supply chain, code execution, memory poisoning, multi-agent communication, cascading failures, human-agent trust exploitation, and rogue agents.
Alibaba Cloud Security Center (SAS) agent onboarding and management assistant. Use this skill when the user wants to onboard servers to Security Center, install the security agent, deploy cloud security protection, connect via proxy, troubleshoot agent offline or installation failures, create image templates with pre-installed agent, view Security Center version and expiration, check authorization quota, upgrade or switch server protection versions, toggle pay-as-you-go feature modules, uninstall the Security Center agent from a server, find servers with specific software installed (e.g. Nginx, MySQL, Redis), or detect security risks (vulnerability scanning, baseline checks, security alert queries).
Safely triage and forensically analyze reported phishing: extract the raw message, inspect the Received chain, verify SPF/DKIM/DMARC, detect display-name and lookalike spoofing, unwrap redirects and SafeLinks/URLDefense, decode quishing QR codes, triage attachments, and extract IOCs for hunting. Use when given a reported phishing email, a suspicious .eml or .msg file, email headers to analyze, a malicious attachment or link to triage, or a business email compromise or spoofing case.
Production-ready Auth.js v5 setup for Next.js and Cloudflare Workers. Use when: setting up authentication, implementing OAuth/credentials/magic links, configuring D1 or PostgreSQL adapters, debugging session issues, migrating from v4 to v5, fixing edge compatibility, troubleshooting JWT/database sessions, resolving AUTH_SECRET errors, fixing CallbackRouteError, or implementing RBAC. Covers: Next.js App Router & Pages Router, Cloudflare Workers + D1, OAuth providers (GitHub, Google, etc.), credentials auth, magic links, JWT vs database sessions, middleware patterns, role-based access control, token refresh, edge runtime compatibility, and common error prevention. Keywords: Auth.js, NextAuth.js, authentication, OAuth, credentials, magic links, D1 adapter, Cloudflare Workers, Next.js middleware, JWT session, database session, refresh tokens, RBAC, edge compatibility, AUTH_SECRET, CallbackRouteError, CredentialsSignin, JWEDecryptionFailed, session not updating, route protection
CloudBase Node SDK auth guide for server-side identity, user lookup, and custom login tickets. This skill should be used when Node.js code must read caller identity, inspect end users, or bridge an existing user system into CloudBase; not when configuring providers or building client login UI.
Manages backup and archive data under retention schedules and erasure obligations. Covers the technical infeasibility exception for backup deletion, backup cycle alignment with retention periods, restore-and-delete procedures, and interim protective measures during backup retention. Activate for backup deletion, archive erasure, backup retention, restore and delete, technical infeasibility queries.
Production-ready authentication framework for TypeScript with first-class Cloudflare D1 support. Use this skill when building auth systems as a self-hosted alternative to Clerk or Auth.js, particularly for Cloudflare Workers projects. Supports social providers (Google, GitHub, Microsoft, Apple), email/password, magic links, 2FA, passkeys, organizations, and RBAC. Prevents 10+ common authentication errors including session serialization issues, CORS misconfigurations, D1 adapter setup, social provider OAuth flows, and JWT token handling. Keywords: better-auth, authentication, cloudflare d1 auth, self-hosted auth, typescript auth, clerk alternative, auth.js alternative, social login, oauth providers, session management, jwt tokens, 2fa, two-factor, passkeys, webauthn, multi-tenant auth, organizations, teams, rbac, role-based access, google auth, github auth, microsoft auth, apple auth, magic links, email password, better-auth setup, session serialization error, cors auth, d1 adapter
Master bug bounty orchestrator — full pipeline: recon, pre-hunt learning, vulnerability hunting (30+ classes), A-to-B chaining, AI/LLM testing (ASI01-ASI10), language-specific grep, bypass tables, and reporting (7-question gate, CVSS 3.1, human-tone templates). Use for ANY bug bounty task — starting a new target, recon, hunting specific vulns, source code audit, AI feature testing, or report writing. 中文触发词：漏洞赏金、安全测试、渗透测试、漏洞挖掘
A C2 framework evasion methodology: analyze C2 source code, search for detection rules (YARA/Sigma/Snort), analyze rule by rule, and modify the source to bypass detection. Use when YARA/Sigma/Snort rules trigger alerts or when a beacon/implant is detected by antivirus. Step one: identify the implant/beacon language and architecture; step two: search for the corresponding detection rules and analyze and modify them one by one
The complete exploitation chain after cloud credentials (AK/SK) are leaked. Use after obtaining cloud platform Access Key and Secret Key through information leaks, .env files, git leaks, or SSRF metadata. Use when credentials in formats such as AWS AKIA*/ASIA*, Tencent Cloud AKIDz*, Alibaba Cloud LTAI* are obtained. Covers the full attack chain from credential configuration → permission enumeration → resource takeover → backdoor persistence. Complements cloud-iam-audit (which focuses on policy analysis) — this skill focuses on hands-on exploitation actions once credentials are obtained. CAM/COS/CVM/SCF exploitation in Tencent Cloud competition scenarios is a key focus. Use this skill whenever any cloud API key, temporary credential, or STS Token is discovered
Cloud IAM permission auditing and privilege escalation. Use when cloud platform credentials (AWS AK/SK, Azure SPN, GCP SA, Tencent Cloud SecretId/SecretKey) are obtained and the permission scope and privilege escalation paths need to be assessed. Covers IAM/CAM policy analysis for AWS/Azure/GCP/Tencent Cloud, common privilege escalation paths (PassRole, AssumeRole, Lambda/SCF escalation), cross-account attacks, and CloudTrail/CloudAudit evasion. Use this skill whenever any cloud credential, AK/SK, or SecretId/SecretKey is discovered
Credential spraying and reuse attacks. Use after usernames/passwords/hashes have been collected and the credentials need to be tested for validity on other services/hosts. Covers password spraying strategy (avoiding lockouts), credential reuse detection, and PTH/PTK attacks. Used to expand the scope of control
Search for threat intelligence, CVEs, malware analysis, breach reports, and security research across 300+ curated security domains (BleepingComputer, Hacker News, Krebs, Unit42, Talos, CISA, Mandiant, Rapid7, Securelist, etc.). Use this skill whenever the user asks to: research a CVE or vulnerability, find what security vendors are saying about a threat actor or malware family, search security blogs, look up threat intelligence on a topic, find recent breach or ransomware reports, collect CTI for a MITRE technique, or push research into NotebookLM. Triggers for phrases like "search security sources", "find threat intel on X", "what are vendors saying about Y", "research CVE-XXXX", "look up malware Z", "collect CTI", "push to NotebookLM", or any domain-scoped web research request in a security context.
Design and audit data export, portability, backup handoff, account deletion, workspace offboarding, migration, machine-readable formats, admin exports, and user trust flows for SaaS, apps, marketplaces, games, and desktop software. Use when users need to export, move, delete, restore, or leave with their data safely.
Harden and monitor a Kubernetes cluster against the attacks that actually happen — RBAC least privilege and escalation paths, Pod Security Admission enforcement, network policy default-deny, secrets and service-account token exposure, control-plane and kubelet exposure, and audit-log-based detection. Use when reviewing a cluster's security posture, responding to a suspected cluster compromise, deciding what to enforce and detect, or translating an attack path from attacking-eks-gke-aks into a defense.
Audit and design enterprise readiness across security review, SSO, SCIM, RBAC, audit logs, admin controls, procurement, legal, privacy, compliance evidence, SLA/support, implementation, pilot, rollout, and expansion. Use when selling SaaS, developer tools, marketplaces, or platforms to larger organizations or preparing an enterprise plan.
Develop working exploits from memory-corruption bugs in native binaries — turning a stack/heap overflow, use-after-free, or type confusion into control flow, an arbitrary read/write, and a shell, and defeating ASLR, NX, stack canaries, PIE, and RELRO along the way. Use when you have a crashing input or a known bug class in an ELF/PE and need a primitive, when building a ROP chain with pwntools and ROPgadget, or when working a CTF pwn challenge or authorized binary exploitation.
Usar para construir un modelo de amenazas chico y acotado sobre el trabajo actual o sobre código nuevo — una feature, un servicio, una API o los cambios de la rama actual. Descompone el sistema en activos, puntos de entrada y fronteras de confianza, enumera amenazas con STRIDE y registra mitigaciones y riesgo residual en un informe trazable con un diagrama de flujo de datos. Se invoca por separado para modelar un componente, o desde otro flujo (fmway-dev después del PRD o el plan, fmway-bugs para una corrección con impacto de seguridad) para exponer amenazas antes de escribir o entregar el código. Especialmente importante para superficies externas nuevas, flujos de autenticación, pagos o datos personales, y cambios en las fronteras de confianza.
Use when migrating a project from the legacy ForgeRock SDK (FRAuth, FRSession, forgerock-ios-sdk, forgerock-android-sdk, @forgerock/javascript-sdk) to the new Ping Identity Journey SDK. Trigger whenever the user mentions migrating, upgrading, porting, or converting ForgeRock code to the Ping SDK — phrases like "ForgeRock to Ping migration", "upgrade FRAuth", "replace FRSession", "move off @forgerock/javascript-sdk", "migrate to @forgerock/journey-client", "upgrade to Ping Journey SDK", or even a vaguer "help me modernize our ForgeRock auth". Works on Android (Kotlin), iOS (Swift), and JavaScript/TypeScript codebases. Preserves old code as comments so rollback is trivial, verifies the app still builds, and writes a line-numbered report of every change.
Use when auditing dependency health — outdated packages, CVE triage with attack-vector weighting, deprecated/declining library detection (trend-watch). Runs `audit-deps.sh` and `audit-trend-watch.sh`. Pairs with `frontend-review-security` for the full security picture.
Use when adding authentication to a project scaffolded with genesis — login, sessions, SSO, admin users. Asks for an auth tier (basic/standard/strict), derives the mechanism from requirements, and implements it in place following the project's existing conventions.
Offline password hash cracking with hashcat. Use when password hashes (NTLM/NTLMv2/Kerberos TGS/AS-REP/SHA/MD5/bcrypt/NetNTLMv2) are obtained and the plaintext password needs to be recovered. hashcat is a GPU-accelerated password cracking tool, dozens of times faster than john. Covers hash type identification, dictionary attacks, rule-based attacks, mask attacks, and combination attacks. Always use this skill after obtaining hashdump/secretsdump/Kerberoast/AS-REP output
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.
Make a single KBAC authorization decision via the IndyKite AuthZEN REST API (`POST /access/v1/evaluation`) - returns a boolean `decision` for one (subject, action, resource) triple, optionally with per-request `context.input_params`. Use for a single yes/no question - "can ada PROVISION gpu-node-7?", "is this user allowed to delete this document?", "gate this operation on a live check", or debugging why one decision is false. Not for many checks at once (use indykite-authzen-evaluations), not for enumerating which actions/resources/subjects are allowed (use indykite-authzen-search-action / -search-resource / -search-subject), and not for authoring the policy behind the decision (use indykite-authzen-kbac-policies). For the same decision over MCP/JSON-RPC see indykite-mcp-server (`authzen_evaluate`).
Run many KBAC authorization decisions in one call via the IndyKite AuthZEN REST API (`POST /access/v1/evaluations`), with top-level subject/action/resource/context as defaults overridden per entry; returns one `decision` per entry, in order. Use when checking a known, fixed set of checks at once - one subject against many resources, one action across many subjects, or any mix of triples - e.g. "of these servers, which can grace provision?", "for each of these users, can they deploy gpu-node-7?". For a single check use indykite-authzen-evaluation; to enumerate ALL allowed actions/resources/subjects (open-ended, not a fixed list) use indykite-authzen-search-action / -search-resource / -search-subject; to author the policy use indykite-authzen-kbac-policies.
List the actions a subject is allowed to perform on a resource via the IndyKite AuthZEN REST API (`POST /access/v1/search/action`) - returns the granted action names for one pinned (subject, resource) pair. Use to enumerate permitted operations - "what can linus do with gpu-node-7?", "which actions does this user have on this item?" (e.g. to render only allowed UI controls). Not for a specific-action yes/no ("can linus DEPLOY gpu-node-7?" -> indykite-authzen-evaluation); to enumerate the other axes use indykite-authzen-search-resource (which resources) or indykite-authzen-search-subject (which subjects); to author the policy use indykite-authzen-kbac-policies.
List the resources a subject is allowed to perform a given action on via the IndyKite AuthZEN REST API (`POST /access/v1/search/resource`) - given a subject and an action, returns the matching resource instances of a type. Use to enumerate permitted resources - "which servers can linus provision?", "list the documents this user can read" (access-filtered feeds). Returns `{type,id}` references, not a yes/no decision and not the resource data itself (for graph data use indykite-ciq-read). For a single-resource yes/no use indykite-authzen-evaluation; to enumerate the other axes use indykite-authzen-search-action (which actions) or indykite-authzen-search-subject (which subjects); to author the policy use indykite-authzen-kbac-policies.
List the subjects allowed to perform a given action on a resource via the IndyKite AuthZEN REST API (`POST /access/v1/search/subject`) - given a resource and an action, returns the matching subject instances of a type. Use to enumerate who has access - "who can provision gpu-node-7?", "list the people allowed to approve this document" (audit / reviewer views). Not for a specific-subject yes/no ("can grace provision gpu-node-7?" -> indykite-authzen-evaluation); to enumerate the other axes use indykite-authzen-search-action (which actions) or indykite-authzen-search-resource (which resources); to author the policy use indykite-authzen-kbac-policies.
Investigate security incidents in Microsoft Azure (resource and subscription control plane) — reconstruct attacker activity from the Azure Activity Log and resource/data-plane diagnostic logs, anchor the investigation on the identity that made the calls (a user, service principal, or managed identity), trace privilege escalation through role assignments, hunt managed-identity token abuse and VM run-command code execution, and detect storage or Key Vault data theft while correlating back to Entra sign-in logs. Use when responding to a suspected Azure resource compromise, anomalous Azure Activity Log entries, a Microsoft Defender for Cloud alert, managed-identity or service-principal abuse, a crypto-mining VM, or storage-account exfiltration.
Investigate a security incident in Google Cloud — establishing what audit logging exists before trusting a gap, reconstructing activity from Cloud Audit Logs, triaging service-account and OAuth abuse, following Security Command Center findings, and scoping IAM and resource changes. Use when responding to a suspected GCP compromise, investigating a leaked service-account key, working a Security Command Center or Event Threat Detection alert, or reconstructing what a principal did across a GCP organization
Investigate security incidents in Microsoft 365 and Entra ID (Azure AD) -- search the Unified Audit Log, correlate sign-in and audit events, trace illicit OAuth consent grants, analyze mailbox rule manipulation, and contain compromised identities. Use when responding to a BEC incident, investigating Entra ID compromise, analyzing suspicious OAuth app permissions, tracing mail forwarding abuse, or reviewing Azure AD sign-in anomalies
A CTF flag judging checklist. Use when determining whether a CTF challenge is complete (whether the flag has been captured), analyzing why an attack failed, or providing precise guidance for the next attack step. Covers flag search and verification, vulnerability discovery assessment, exploitation assessment, flag location inference, and common challenge pattern matching (SQLi/LFI/RCE/IDOR/SSRF/deserialization)
Give an AI agent an encrypted inbox and agent-to-agent messaging CLI. Use when agents need stable inbox addresses, durable encrypted threads, signed shared channels, async multi-agent handoffs, human approvals, device-key recovery, or JSON automation.
A security testing methodology for the MCP (Model Context Protocol) protocol. Triggers when the target environment uses MCP Servers to integrate external tools, when the security of MCP tool descriptions needs to be assessed, or when testing the security boundaries of Agents invoking tools via MCP. Covers: tool description poisoning, rug pull attacks (dynamic tampering), instruction override (Shadow Tool), hidden instructions (ANSI/Unicode), cross-Server attacks, token theft, schema manipulation, and context overflow.
Detect, analyze, and remediate OWASP A10:2025 — Mishandling of Exceptional Conditions in Python web applications (FastAPI and Flask). Use this skill whenever the user asks about error handling security, exception management, fail-open vulnerabilities, stack trace exposure, uncaught exceptions, transaction rollback safety, or resource leaks in exception paths. Also trigger for any OWASP A10 audit, security code review involving try/except blocks, global exception handlers, or HTTP error responses that may leak sensitive information. If the user mentions CWE-209, CWE-248, CWE-636, CWE-703, CWE-754, or CWE-476 in a Python context, use this skill immediately.
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.