What problem does it solve? Paywall and subscription flaws often hide behind client-side tricks like CSS overlays or DOM hiding, making it hard to know whether the server actually enforces entitlement checks. This Skill provides an evidence-gated workflow to verify that premium content and subscription APIs are truly protected on the server side, using only your own authorized test accounts. ## Core Features & Use Cases - Baseline-to-Probe Workflow: Follows a fixed sequence of baseline capture, single-variable probes, post-baseline comparison, and oracle verification so every finding is backed by reproducible evidence. - False Positive Filtering: Distinguishes real entitlement bypasses from CSS hiding, browser caching, and public previews, and treats WAF blocks or scanner hits as inconclusive rather than vulnerabilities. - Safe Boundary Enforcement: Stops immediately when real paid content, third-party subscriptions, or irreversible side effects are involved, and routes payment-state issues to payment workflow testing and cache issues to cache deception testing. - Use Case: You maintain a subscription product and want to confirm that a free-tier test account cannot retrieve premium canary content through the content API or cached responses while the authoritative entitlement ledger shows no grant. ## Quick Start Ask the agent to use hunt-paywall-entitlement to plan an authorized validation of whether your free test account can access premium canary content through the entitlement API.
