webhook-setup

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

• Third-party content exposure detected (high risk: 1.00). The skill's SKILL.md and examples explicitly ingest and parse webhook payloads from third-party providers (e.g., Stripe, GitHub, Slack) via /webhooks endpoints, treating those untrusted, user-generated payloads as inputs that drive routing, database updates, and CI triggers—so external content can materially influence actions.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

• Direct money access detected (high risk: 1.00). The skill explicitly targets payment gateway integrations: it names providers like Stripe and PayPal and includes a concrete Stripe webhook example that verifies Stripe signatures and routes payment-related events (e.g., payment_intent.succeeded, invoice.payment_failed) to handlers that update order/payment state in a database. This is a specific, payment-gateway–oriented integration (not a generic webhook tutorial), so it qualifies under "Payment Gateways" for Direct Financial Execution.