setuplisted

# Browser Bridge — Setup This is a delegating stub. The full install + setup flow lives at one canonical URL so it stays in sync across direct paste-from-the-web installs and `/claude-browser-bridge:setup` invocations from inside an existing Claude session. ## What to do 1. Fetch the canonical install document: ```bash curl -fsS https://browser-bridge.softwaresoftware.dev/install.txt ``` 2. Follow every phase in order. That document is the operator script for end-to-end setup: rules, marketplace bootstrap, plugin + daemon install, loading the extension (the one manual step), an end-to-end verification with `list_tabs`, and hand-off. 3. If `install.txt` is unreachable (network down, the static site is being redeployed, etc.), fall back to the steps below — the same flow, condensed. install.txt is the source of truth when reachable. ## Why this is a stub The install flow exists in one place — `install.txt` at the URL above — so that: - A user on a fresh machine pastes the URL into Claude Code and gets the same flow - A user already inside a Claude session can run `/claude-browser-bridge:setup` and get the same flow - The flow updates in one place; no drift between two copies When operating from this skill, you ARE the install agent install.txt addresses in second person. Read it, then act. ## Fallback (only if install.txt is unreachable) The plugin is already installed if you're running this skill, so skip the marketplace/install phases and go straight to t