Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-browser-persistence

competition-browser-persistence

Verified

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for browser cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, service workers, offline caches, and client-side session persistence. Use when the user asks to inspect browser state, replay cached auth or session behavior, explain why a page behaves differently after load, or trace how stored client state changes requests, rendering, or access. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

FileKindSize
SKILL.mdskill md3.1 KB
agents/openai.yamlconfig407 B
references/browser-persistence.mdmarkdown1.1 KB

references/browser-persistence.md

View on GitHub
# Browser Persistence Checklist

## Surfaces To Check

- Cookies: domain, path, expiry, `HttpOnly`, `Secure`, `SameSite`
- `localStorage`, `sessionStorage`, IndexedDB object stores, Cache Storage entries
- Service worker registrations, cached responses, fetch handlers, offline fallbacks
- Boot-time globals, hydration payloads, feature flags, role or tenant selectors

## Correlation Pattern

1. Storage item or cookie identified
2. Origin and scope confirmed
3. Request, render, or cache behavior linked to that item
4. Clean-state vs mutated-state run compared
5. Decisive branch reproduced

## Evidence To Keep Together

- State identity: origin, key, value shape, scope, expiry, DB or cache name
- Runtime effect: header, route, feature flag, cached response, or rendered branch
- Replay prerequisites: initial route, prior request, login state, or service worker registration

## Common Pitfalls

- Listing storage contents without showing which item changes behavior
- Mixing several origins or tenants in one storage explanation
- Treating cached UI data as backend authorization without proving a server-side effect
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall