Agent Skill

Multi Account Isolation skill

multi-account-isolationantibrow/anti-detect-browser-skillsmulti-account-isolation/SKILL.md

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.

19MIT

always on

220 tokname + description

once used

2,356 tokSKILL.md body

bundled files

installs

102kskills.sh

Install the Multi Account Isolation skill

Skills CLI (Claude Code, Codex, Cursor and others)

npx skills add https://github.com/antibrow/anti-detect-browser-skills --skill multi-account-isolation

Claude Code, by hand (all projects)

git clone --depth 1 https://github.com/antibrow/anti-detect-browser-skills.git /tmp/anti-detect-browser-skills
mkdir -p ~/.claude/skills
cp -R /tmp/anti-detect-browser-skills/multi-account-isolation ~/.claude/skills/multi-account-isolation

For one project only, copy the folder into .claude/skills/ in that project instead. The agent picks it up when a task matches its description.

What it costs your context

Agent Skills load in three steps. Tokens counted with the o200k tokenizer; your model's count will differ a little.

When	What loads	Cost
Every session	Name and description	220 tok
When the agent uses it	The SKILL.md instructions	2,356 tok
Only if opened	No bundled files	—

Until it is used, multi-account-isolation costs about 6.2× less than the median MCP server we measured (1,363 tokens on every turn). Installing all 4 skills from antibrow/anti-detect-browser-skills would load 665 tokens of descriptions. Skills vs MCP study

Checks

Our checks found nothing to flag: it follows the Agent Skills specification's naming and size guidelines and doesn't pipe downloads into a shell.

Checked 2026-10-22 · method

What's inside

The headings of its SKILL.md. Read the full file on GitHub.

Profile Isolation - verifying it, not assuming it
The configuration invariant
Setup under test
The checks
Reading a failure
What the runtime touches, and how to check it
What isolation cannot cover
Acceptable use
Related Skills

More skills from antibrow/anti-detect-browser-skills

All skills in this repo

anti-detect-browserantibrow/anti-detect-browser-skills
Drive Chromium from standard Playwright APIs with a real-device fingerprint applied in the kernel, one persistent isolated profile per identity, and a per-profile proxy whose exit IP sets timezone and WebRTC - JavaScript (npm 'anti-detect-browser') or Python (PyPI 'antibrow'). Use when sessions must stay logged in across runs and stay separate, when a scraper or agent is blocked by an incoherent headless fingerprint, when checking ads or pricing from another region, when a page must be reached as a phone rather than a desktop, when automation mints a profile per task, when running several of your own accounts from one machine, or when testing how your own bot detection scores a real device. Also for 'antibrow', 'fingerprint browser', 'multi-account browser', '防关联', '多账号', '安卓模拟', 'Android profile', 'mobile fingerprint', 'temporary profile', 'CreepJS', 'residential proxy', 'browser-use', 'crawl4ai'. MCP control is browser-mcp-agent; isolation is multi-account-isolation.
133k222 tok idle · 8,873 in use
browser-mcp-agentantibrow/anti-detect-browser-skills
Give an AI agent its own real browser over MCP tool calls - launch, navigate, click, fill, screenshot, extract text, run JS - with a kernel-level real-device fingerprint and a persistent profile, so the session stays logged in between runs and pages see one coherent device instead of a headless build. No Playwright or SDK code to write. Use when an agent should operate a site itself, when a computer-use / browser-use setup needs a captured real fingerprint rather than a synthetic one, when agent sessions keep losing their login, or when comparing hosted agent-browser services. Also for 'MCP browser', 'browser MCP server', 'let my agent browse the web', 'agent browser control', 'browser-use MCP', 'computer use browser', 'Browserbase alternative', 'Steel browser alternative', 'headless browser detected'. Node (npx) or Python; Windows x64, macOS Intel + Apple Silicon, Linux x64 / arm64. SDK and REST reference is anti-detect-browser; account isolation is multi-account-isolation.
102k216 tok idle · 3,596 in use