[codex] add context sync skill

[shubh24]

What changed

• adds a context-sync skill for copying durable local Chromium profile state into a Browserbase Context
• archives localStorage, IndexedDB, Cache Storage, service workers, bookmarks, history, preferences, OPFS, and extension data
• transfers cookies separately through CDP so macOS and Windows cookie encryption does not break in Browserbase's Linux runtime
• documents the persistence boundary, encryption/upload format, safety requirements, and known exclusions
• adds the skill to the repository README

Why

cookie-sync only transfers cookies. Users who need a cloud session to retain broader disk-backed browser state currently have no packaged workflow for uploading a portable profile snapshot into a Browserbase Context.

Impact

Agents can use one guarded workflow to create or refresh a Context from a local Chrome profile. The skill requires explicit permission before closing Chrome, excludes caches and non-portable credential databases, and does not claim to restore live tabs, JavaScript state, saved passwords, or sessionStorage.

Validation

• node scripts/validate-skills.mjs --skill context-sync
• skill-creator quick_validate.py
• node --check skills/context-sync/scripts/context-sync.mjs
• synthetic-profile dry run covering all included storage categories and exclusion rules

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​browserbasehq/​stagehand@​3.7.1
	npm/​adm-zip@​0.5.18
	npm/​@​browserbasehq/​sdk@​2.16.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @browserbasehq/stagehand is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: skills/context-sync/package-lock.json → npm/@browserbasehq/stagehand@3.7.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@browserbasehq/stagehand@3.7.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report