stripe-payment-debugging

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

• Third-party content exposure detected (high risk: 0.85). The required runtime workflow uses cofounder run stripe-list-events and other cofounder run stripe-* tools to ingest Stripe event/object data (outsider-authored content from Stripe’s public API responses) into the agent’s LLM context.

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

• Direct money access detected (high risk: 1.00). The skill is specifically designed for Stripe (a payment gateway) and exposes explicit Stripe-focused CLI tools (e.g., stripe-list-events, stripe-get-customer, stripe-get-subscription, stripe-list-invoices, stripe-list-charges, get_stripe_webhook_destination, cofounder run sync_stripe_env). These are purpose-built for payment platform operations and the doc even refers to mutating Stripe (e.g., refunds or env sync) when explicitly requested. Because it is a Stripe-specific toolset for payment operations, it meets the "Direct Financial Execution" criteria.