What problem does it solve? CTF and web challenges often hide the decisive logic 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, then tying stored state to concrete request, rendering, or access-control effects. ## 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. - State-to-Behavior Correlation: Show how stored items become 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 persisted state to the resulting capability. - Use Case: During a CTF web challenge, a page behaves differently after login. Use this Skill to identify which cookie or storage key drives the changed branch, then replay the minimal stateful sequence that reaches the hidden route. ## Quick Start After $ctf-sandbox-orchestrator is active, use $competition-browser-persistence to inspect the browser cookies, storage, and service workers in this challenge and replay the smallest stateful path that reaches the hidden branch.
