Skip to content
InfratoApp
InfratoApp / Resources / Agent skills / multi-account-isolation

multi-account-isolation

multi-account-isolation is an agent skill published by antibrow, listed under building agents. It lives in the antibrow/anti-detect-browser-skills repository, which has 20 GitHub stars and is licensed under MIT; we last read it on 2026-09-16.

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', 'canvas hash unstable', 'account association', 'temporary profile', '防关联', '多账号', '隔离自检'. The SDK is anti-detect-browser; MCP is browser-mcp-agent.

Install

skills is a generic installer for any repository of Claude agent skills -- it reads antibrow/anti-detect-browser-skills’s own structure rather than assuming one, the same way this page reads the skill’s own SKILL.md rather than assuming a format.

npx skills add antibrow/anti-detect-browser-skills

Maintenance

Stars
20
State
listed
Licence
MIT
From the repository

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', 'canvas hash unstable', 'account association', 'temporary profile', '防关联', '多账号', '隔离自检'. The SDK is anti-detect-browser; MCP is browser-mcp-agent.

multi-account-isolation compared with similar skills

multi-account-isolation compared with other skills for the same job, by publisher, what it does, repository stars and last update
SkillPublisherWhat it doesRepo starsLast update
multi-account-isolation (this page)antibrowVerify that browser profiles are actually isolated from one another instead of assuming it - confirm each pro…202026-08-28
anti-detect-browser(same repository)antibrowDrive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persis…202026-08-28
browser-mcp-agent(same repository)antibrowGive an AI agent its own real browser over MCP tool calls - launch, navigate, click, fill, screenshot, extrac…202026-08-28
claude-handoffmattpocockHand the current conversation off to a fresh background agent that picks up the work immediately.303,5492026-10-22
context-engineeringaddyosmaniOptimizes agent context setup. Use when starting a new session, when agent output quality degrades, when swit…110,6112026-10-13
using-agent-skillsaddyosmaniDiscovers and invokes agent skills. Use when starting a session, or when you need to decide which skill or wo…110,6112026-10-13
agent-platform-inferencegoogleConnects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemin…21,5802026-10-25

Skills from the same repository first, then others for this job by repository stars. Figures are from each repository when we last read it.

Common questions about multi-account-isolation

What does multi-account-isolation do?
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', 'canvas hash unstable', 'account association', 'temporary profile', '防关联', '多账号', '隔离自检'. The SDK is anti-detect-browser; MCP is browser-mcp-agent.
How do I install multi-account-isolation?
Run npx skills add antibrow/anti-detect-browser-skills. The skills installer reads the repository’s own structure, so it works for any repository of agent skills.
Who publishes multi-account-isolation?
antibrow.
Is multi-account-isolation maintained, and what licence does it use?
Its repository has 20 GitHub stars and its state in our directory is listed. Its last commit we recorded was on 2026-08-28. The repository declares the MIT licence.

More agent skills for building agents

All building agents entries →

Learn this on Infrato