Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
中文简介正在准备中。当前显示原文说明。
4880 个 · 按相关度排序
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities
中文简介正在准备中。当前显示原文说明。
AUTHORIZED USE ONLY: This skill contains dual-use security techniques. Before proceeding with any bypass or analysis: > 1.
中文简介正在准备中。当前显示原文说明。
Builds production-ready REST API endpoints with validation, error handling, authentication, and documentation. Follows best practices for security and scalability.
中文简介正在准备中。当前显示原文说明。
Orchestrate multiple Antigravity skills through guided workflows for SaaS MVP delivery, security audits, AI agent builds, and browser QA.
中文简介正在准备中。当前显示原文说明。
Audits GitHub Actions workflows for security vulnerabilities in AI agent integrations including Claude Code Action, Gemini CLI, OpenAI Codex, and GitHub AI Inference. Detects attack vectors where attacker-controlled input reaches. AI agents running in CI/CD pipelines.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user asks about hazardous materials (hazmat) transportation under 49 CFR 171-180 — placarding requirements, segregation tables, hazmat employee training (49 CFR 172 Subpart H), Hazmat Safety Permit (HMSP), shipping papers, packaging groups, emergency response phone, security plans, hazmat endorsement on CDL, and bulk vs non-bulk distinctions. Cite specific 49 CFR section.
中文简介正在准备中。当前显示原文说明。
Use this skill when the user asks about CDL classes (A, B, C), endorsements (H, N, P, S, T, X), required for hazmat / passenger / school bus / tank / triple-trailer operations, what each class is permitted to operate, the TSA Security Threat Assessment for hazmat, and ELDT (Entry-Level Driver Training) requirements. Cite 49 CFR 383.
中文简介正在准备中。当前显示原文说明。
Refute-before-prove research discipline: automated counterexample sweeps before any formalization, meter-integrity audits for information-bound experiments, mutation-tested model checkers, pre-registered commit-or-cut gates for speculative directions, wrong-turn reporting, and numeric-claim provenance. Use when validating any new theorem, bound, equilibrium, or security claim; when building or trusting a checker, simulator, or experiment; or when deciding whether a speculative research direction lives or dies. NOT for exploratory brainstorming, product prioritization, writing style, or literature review.
中文简介正在准备中。当前显示原文说明。
Defensive counterpart to federated-harbor-redteam: closes the smells that red team opens against The Federated Harbor whitepaper. Federation-specific defenses for cross-harbor primitives — mechanization commitments, scope hedges, cross-paper dependency formalization, pre-emptive analogies (CT, Macaroons, atomic swaps), and defense-in-depth framing (refuses vs prices). Use during a versioned red-vs-white round; pairs with federated-harbor-redteam. NOT for ad-hoc code review, NOT for the Anchor or Bonded papers (use whitehat-defense).
中文简介正在准备中。当前显示原文说明。
Adversarial reviewer for The Federated Harbor whitepaper — the third paper in the Curiositech sequence after Anchor and Bonded Commons. Probes federation-specific threats: trust transitivity, cross-harbor token forgery, federated revocation under partition, cross-harbor Sybil, cross-domain settlement, equivocation, bond-pool draining, cold-start joining, federation-operator Sybil. Use during a versioned red-vs-white round; pairs with federated-harbor-whitehat. NOT for incident response, NOT for the Anchor or Bonded papers (use redteam-review).
中文简介正在准备中。当前显示原文说明。
Use when optimizing Docker builds with BuildKit, designing multi-stage Dockerfiles, leveraging cache mounts, building multi-arch images, choosing distroless vs alpine, or signing images with cosign. Triggers: docker build slow, layer cache not hitting, npm install / pip install reruns, multi-stage final image bloat, glibc vs musl issues, RUN --mount=type=cache, BUILDKIT_INLINE_CACHE, registry cache exporters, qemu emulation for arm64, COPY ordering for cache. NOT for Docker daemon admin, Kubernetes-specific image policies, container security scanning workflows, or Buildpacks (different paradigm).
中文简介正在准备中。当前显示原文说明。
Write production-grade Dockerfiles, docker-compose configurations, multi-stage builds, and container optimization. Activate on "Dockerfile", "docker", "docker-compose", "container", "multi-stage build", "docker image", "container optimization", "docker security". NOT for Kubernetes orchestration, cloud-specific container services (ECS, Cloud Run), or CI/CD pipelines (use github-actions-pipeline-builder).
中文简介正在准备中。当前显示原文说明。
Practical incident-response runbook for a suspected or confirmed ComfyUI / GPU-daemon compromise. Triage, scope, contain, forensic collection, weight-integrity verification, rebuild from clean snapshot, postmortem. NOT for hygiene scans on a healthy box (use supply-chain-defense-for-ml-extensions), and NOT for runtime hardening of a fresh deployment (use gpu-hosted-asset-hardening).
中文简介正在准备中。当前显示原文说明。
Audit whether an enforced-coordination MCP has actually shrunk its ~19 legacy etiquette verbs into the 5 enforced tools — work/act/ask/recall/status — each carrying one denial shape and one transcript event, migrated through a real retirement path (intake-metadata, alias, or doc-history — never a parallel runtime), with zero legacy-verb calls once a body reaches compliance mode C4+. Use when reviewing a broker-collapse migration plan, gating a body's move from advisory (C0-C3) to enforced (C4+) coordination, or verifying IT-018 Broker Collapse compliance. NOT for the inbound trigger→spawn boundary that decides whether an event may spawn an agent at all (use fleet-event-spawn-trust), the capability-token cryptographic mechanism behind a denial (use agentic-zero-trust-security), designing how a swarm of agents invokes and shards work (use swarm-invocation-designer), or auditing an individual PR's mergeability (use agent-pr-authoring).
中文简介正在准备中。当前显示原文说明。
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
中文简介正在准备中。当前显示原文说明。
Build, debug, optimize, and deploy ComfyUI workflows for diffusion image, video, and audio generation. Activate on: ComfyUI workflow, ComfyUI custom node, ComfyUI API, ComfyUI Manager, KSampler, FLUX in ComfyUI, Wan 2.2 ComfyUI, Hunyuan video ComfyUI, LTX video ComfyUI, IPAdapter, ControlNet ComfyUI, Kijai wrapper, ComfyDeploy, RunComfy, ComfyUI security, GGUF quantization, TeaCache, Nunchaku, ACE-Step ComfyUI, F5-TTS ComfyUI, subgraphs ComfyUI. NOT for: A1111/Forge/Invoke (different UIs), training pipelines from scratch, non-diffusion ML models, or general image-API integrations (use generative-video-2026 / generative-music-audio / media-gen-deployment).
中文简介正在准备中。当前显示原文说明。
Safety-case design for always-on agents with episodic memory. Covers data hygiene, privacy and security risk surfaces, cost controls, scope, user dependency concerns, retention, incident containment, and responsible deployment evidence. It identifies hazards and asks for named controls, tests, owners, and residual uncertainty; it does not provide legal, clinical, youth-safety, or jurisdictional determinations. Activate on: "agent safety", "always-on agent privacy", "agent cost control", "persistent agent risks", "AI companion safety", "agent data hygiene", "runaway agent costs", "parasocial AI risk", "/always-on-agent-safety". NOT for: architecture design (use always-on-agent-architecture), input design (use always-on-agent-inputs), application brainstorming (use always-on-agent-applications), healthcare compliance specifically (use hipaa-compliance).
中文简介正在准备中。当前显示原文说明。
Configure an AI agent to send OpenTelemetry traces to Coval. Use when a user wants to add Coval tracing, instrument an agent for simulations or conversation monitoring, make traces show up in Coval, handle SIP/PSTN/WebSocket trace correlation, or replace the one-command wizard with a security-reviewable manual setup.
中文简介正在准备中。当前显示原文说明。
Super-Admin-only lock-down pattern. Use before touching admin.admins, admin.admin_audit_log, is_super_admin() / requireSuperAdmin() / selectIsSuperAdmin, app/api/admin/admins/**, app/(admin)/administration/users/admins/**, the admin RPCs (admin_promote, admin_update, admin_revoke, admin_list, admin_list_audit, admin_find_user_by_email), createAdminClient(), a new RLS policy, SECURITY DEFINER RPC, or admin-gated route, or when locking a sensitive table to Super Admin.
中文简介正在准备中。当前显示原文说明。
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Use when the user explicitly asks to threat model a codebase or path, enumerate abuse paths, or perform AppSec threat modeling.
中文简介正在准备中。当前显示原文说明。
AgentShieldを使用してClaude Codeの設定(.claude/ディレクトリ)のセキュリティ脆弱性、設定ミス、インジェクションリスクをスキャン。CLAUDE.md、settings.json、MCPサーバー、フック、エージェント定義をチェック。
中文简介正在准备中。当前显示原文说明。
Laravelセキュリティベストプラクティス — 認証/認可、バリデーション、CSRF、マスアサインメント、ファイルアップロード、シークレット、レート制限、セキュアなデプロイメント。
中文简介正在准备中。当前显示原文说明。
認証の追加、ユーザー入力の処理、シークレットの取り扱い、APIエンドポイントの作成、決済/センシティブ機能の実装時に使用。包括的なセキュリティチェックリストとパターンを提供。
中文简介正在准备中。当前显示原文说明。
包括的なPerlセキュリティ — テイントモード、入力バリデーション、安全なプロセス実行、DBIパラメータ化クエリ、Webセキュリティ(XSS/SQLi/CSRF)、perlcriticセキュリティポリシー。
中文简介正在准备中。当前显示原文说明。