Multi Account Isolation

Multi-account-isolation is a verification checklist for browser profiles, not another way to spin up identities. Its core idea is that you shouldn't assume profiles are isolated, you should assert it: timezone matching the exit IP, WebRTC leaking only the proxy, canvas and WebGL hashes staying stable across relaunches, and no two profiles sharing a persona, cookie jar, or address. The check table is the useful part, and checks 1, 3 and 7 are cheap and deterministic enough to wire into CI. It is scoped to identities you own or are authorized to operate, and it is honest that a clean result only proves the browser layer is consistent, not that a site won't connect accounts through other signals.

skills.sh installs: 123.9K
GitHub stars: 21
last updated: Oct 26, 2026

View on GitHub

Install

$ npx -y skills add antibrow/anti-detect-browser-skills --skill multi-account-isolation --agent claude-code

Installs into .claude/skills of the current project.

Files

Profile Isolation - verifying it, not assuming it

A profile that looks isolated usually is not. The failures are boring and mechanical: a timezone that does not match the exit IP, a WebRTC candidate carrying the real address, a canvas hash that changes on every read, two profiles that ended up on the same persona. This skill is the check list for catching those before they matter.

Authorized use only. This is for identities you own or are authorized to operate: your own accounts, your own test fixtures, your own QA fleet, and your own anti-fraud stack. It is not for accessing systems without authorization, for accounts that are not yours, or for creating fake accounts or engagement. Comply with the terms of the sites you automate and with applicable law - see Acceptable use.

SKILL.md on GitHub