multi-account-isolation
Verify that browser profiles are actually isolated from one another instead of assuming it - confirm each profile's timezone agrees with its own exit IP, that WebRTC exposes only the proxy, that canvas and WebGL hashes stay identical across relaunches of one profile, and that no two profiles share a persona, a cookie jar, or an address. Use when several of your own accounts or test identities run from one machine and the setup needs checking, when a profile tested clean but something still looks off, when choosing which detection suites to run (CreepJS, whoer, browserleaks WebRTC, pixelscan, liarjs), when auditing what a vendor runtime does with API and proxy credentials, or when asking which layers browser isolation cannot cover at all. Also for 'profile isolation check', 'fingerprint consistency test', 'timezone mismatch', 'WebRTC leak'
Install
npx skills add https://github.com/antibrow/anti-detect-browser-skills --skill multi-account-isolationThe installer uses the repository’s current default branch. The source link shows the exact snapshot recorded by the directory.
Manual install (any agent)
- Download the
multi-account-isolationfolder from the repository. - Place it in your agent’s skills directory.
- Restart the agent; it reads
SKILL.mdon load.
Agent compatibility
There is no agent compatibility evidence for this listing yet.
Source and rankings
View the pinned SKILL.md file- skills.sh · all timeRank 390 · 135,915 installs
- skills.sh · trendingRank 268 · 1,219 weekly installs