What problem does it solve? Integrating paid APIs like Stripe, Toss, Twilio, or Google Maps exposes your app to leaked keys, webhook forgery, duplicate charges, and cost explosions. This Skill gives you a structured security review so you catch these risks before production. ## Core Features & Use Cases - 6-Layer Defense Checklist: Covers network boundary (BFF isolation), HMAC signing and idempotency, abuse detection, payment hardening, key-leak response, and observability logging. - 5 Adversarial Tests: Verifies no secrets in frontend bundles, blocks direct API calls, enforces idempotency on duplicate payments, rejects forged webhook signatures, and triggers anomaly detection on cost spikes. - API Design Review: Evaluates protocol choice (REST, GraphQL, tRPC, gRPC), pagination, N+1 queries, error formats, and versioning strategy. - Use Case: Before launching a Stripe checkout flow, run this Skill to confirm webhook signatures are verified on the raw body, amounts are recalculated server-side, and Idempotency-Key headers prevent duplicate charges. ## Quick Start Ask the agent to audit your Stripe payment integration for security risks and produce the six-layer defense checklist.