competition-browser-persistence — Claude Code skill
competition-browser-persistence — a skill for Claude Code that investigates browser persistence surfaces in CTF sandboxes. It activates when stored client state alters request flows, rendering, or access rules.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a claude-codeWhat competition-browser-persistence does
This skill inspects browser-held data including cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, and service workers. Before mutating values, it records scope, domain, path, origins, and expiration dates, isolating runtime modifications from boot-time state.
The workflow maps client storage, evaluates clean versus mutated states one variable at a time, and reduces findings to the shortest sequence reaching the target branch. It draws inspection rules and checklists from references/browser-persistence.md.
Execution requires $ctf-sandbox-orchestrator to run beforehand. If sandbox assumptions and ownership boundaries are not already established by that orchestrator, the skill routes back to it.
What it helps with
- inspect client-side storage surfaces in CTF environments
- trace how cached tokens and service workers modify HTTP requests
- isolate clean-state from mutated-state execution paths
- reproduce the minimal chain leading to restricted routes
Example prompts for the agent
- Inspect cookies and localStorage to identify which parameter unlocks the admin route
- Compare clean session state against cached storage to trace offline fallback logic
- Extract the minimal persistence chain that persists auth tokens across page reloads
How to install competition-browser-persistence
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a claude-code2Manually: put the files in place
~/.claude/skills/competition-browser-persistence/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-browser-persistence/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a codex2Manually: put the files in place
.agents/skills/competition-browser-persistence/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a cursor2Manually: put the files in place
.cursor/skills/competition-browser-persistence/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-browser-persistence/SKILL.md2Manually: put the files in place
.github/skills/competition-browser-persistence/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-browser-persistenceManually: put the files in place
.devin/skills/competition-browser-persistence/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-browser-persistence
How to install competition-browser-persistence in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-browser-persistence -a claude-code in your terminal.
What does competition-browser-persistence do?
It examines client-side persistence mechanisms in web CTF challenges, tying cookies, cache entries, and service worker states to concrete application behavior.
What is required before using competition-browser-persistence?
The $ctf-sandbox-orchestrator skill must be active first to define sandbox assumptions, evidence priorities, and node ownership.
Source text
SKILL.md · MIT
--- name: competition-browser-persistence description: 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. --- # Competition Browser Persistence Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the decisive branch lives in browser-held state rather than only in visible HTML or backend source. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Identify the active persistence surface first: cookie jar, localStorage, sessionStorage, IndexedDB, Cache Storage, or service worker. 2. Record origin, scope, domain, path, expiry, and key names before mutating state. 3. Tie stored state to one concrete effect: request header, rendered branch, cached response, offline behavior, or hidden route access. 4. Separate boot-time state from runtime-mutated state. 5. Reproduce the smallest stateful sequence that reaches the decisive branch. ## Workflow ### 1. Map Browser State Surfaces - Inspect cookies, storage buckets, service worker registrations, cache entries, and transient globals exposed during boot. - Record which origin, host, route, or feature flag each state item actually applies to. - Keep auth tokens, refresh material, CSRF state, cached responses, and feature toggles in separate evidence blocks. ### 2. Tie State To Runtime Behavior - Show how stored state becomes request headers, role derivation, route visibility, cached API data, or offline fallback behavior. - Compare clean-state and mutated-state runs with one variable changed at a time. - Distinguish UI-only state from backend-accepted state. ### 3. Reduce To The Decisive Persistence Chain - Compress the result to the smallest chain: initial page or login -> state persisted -> subsequent request or render branch -> resulting capability. - Keep extracted storage, service worker scripts, and replay steps tied to the same origin and route. - If the problem broadens into general web routing or worker behavior outside browser persistence, switch back to the broader web-runtime skill. ## Read This Reference - Load `references/browser-persistence.md` for the browser-state checklist, service-worker checklist, and evidence packaging. ## What To Preserve - Cookie attributes, storage keys, database names, cache keys, service worker scopes, and origin boundaries - The exact request or render effect caused by each decisive state item - Clean-state vs mutated-state reproduction steps for the smallest working path
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill