What problem does it solve? CTF sandbox challenges often hide the decisive branch in browser-held state rather than visible HTML or backend source. This Skill provides a structured workflow for inspecting cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, and service workers to explain why a page behaves differently after load and how stored client state changes requests, rendering, or access. ## Core Features & Use Cases - Browser State Mapping: Enumerate cookie jars, storage buckets, service worker registrations, cache entries, and boot-time globals with origin, scope, and expiry recorded before mutation. - State-to-Behavior Correlation: Tie stored state to concrete effects such as request headers, role derivation, route visibility, cached API data, or offline fallback behavior, comparing clean-state and mutated-state runs. - Decisive Chain Reduction: Compress findings to the smallest reproducible sequence from initial page or login through state persistence to the resulting capability. - Use Case: During a CTF web challenge, a page grants different access after a prior visit. Use this Skill to identify which cookie or IndexedDB entry drives the role change, then reproduce the minimal stateful sequence that reaches the hidden branch. ## Quick Start Ask the agent to inspect the browser storage and cookies for the challenge origin and explain which stored item changes the page's behavior after reload.
