- name
SKILL.md
Die Skill-Datei bleibt im Repository des Herausgebers.
Fügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add antibrow/anti-detect-browser-skills --skill multi-account-isolation -a cursor -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add antibrow/anti-detect-browser-skills --skill multi-account-isolation -a claude-code -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add antibrow/anti-detect-browser-skills --skill multi-account-isolation -a codex -yFügen Sie den kopierten Befehl in ein Terminal ein. Er installiert diese SKILL.md in dem jeweiligen Agenten.
npx skills add antibrow/anti-detect-browser-skills --skill multi-account-isolation -a grok -ySenden Sie die kopierte Nachricht in einem Grok Bot-Chat. Der Bot ruft diese SKILL.md von GitHub ab und fügt sie den Skills hinzu, die alle Ihre Bots gemeinsam nutzen.
Install this skill: https://github.com/antibrow/anti-detect-browser-skills/tree/HEAD/multi-account-isolationVom Herausgeber
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.
What this does not claim. Passing every check below means the browser layer is internally consistent. It does not mean a given site will treat two profiles as unrelated: things entirely outside the browser - a shared payment instrument, a shared contact detail, identical activity patterns - are not something any browser setting reaches. Treat a clean result as "the technical layer is not the problem", not as a guarantee.
For the SDK that creates and launches these profiles, see the anti-detect-browser skill.
One identity gets one of everything. Any cell shared between two identities is a defect to find:
identity → profile → persona → proxy → timezone
1 : 1 : 1 : 1 : 1
Profiles are unlimited and free on every antibrow plan, so there is never a reason to reuse one. "Log out and log back in as the other identity" inside one profile defeats the entire setup - the cookie jar and localStorage are the point.
import { AntiDetectBrowser } from 'anti-detect-browser'
const ab = new AntiDetectBrowser({ key: process.env.ANTI_DETECT_BROWSER_KEY })
const identities = [
{ profile: 'fixture-us-01', proxy: process.env.PROXY_US_1, tags: ['Windows 10', 'Chrome'] },
{ profile: 'fixture-us-02', proxy: process.env.PROXY_US_2, tags: ['Apple Mac', 'Safari'] },
{ profile: 'fixture-de-01', proxy: process.env.PROXY_DE_1, tags: ['Windows 10', 'Edge'] },
]
for (const id of identities) {
const { browser, page } = await ab.launch({
profile: id.profile, // isolated cookies, storage, login state
proxy: id.proxy, // from the environment, one per identity
fingerprint: { tags: id.tags }, // drawn once, frozen, replayed after
label: id.profile, // address-bar tag drawn by the kernel, unreadable from the page
})
// ... run the checks below, then ...
await browser.close()
}
Python, same on-disk profile format:
import os
from antibrow import launch
with launch(
profile="fixture-us-01",
proxy=os.environ["PROXY_US_1"], # from the environment, never a literal
geoip=True, # timezone + WebRTC follow the proxy exit
label="fixture-us-01",
) as browser:
page = browser.new_page()
print(browser.timezone, browser.public_ip)
Run each profile through its own proxy, and assert rather than eyeball.
Checks 1, 3 and 7 are the ones worth wiring into CI: they are cheap, deterministic, and they catch the defects that actually recur.
Work down in this order, cheapest first - a fingerprint is almost never the actual cause:
list_profiles, or compare browser.profile_dir per identity. Two identities in one directory explains everything else. Directories are named after the profile's id, not its name, so match on profile.json inside rather than on the folder name.public_ip is distinct.browser.timezone and browser.public_ip together.profile_dir or the cache directory changed under it.Any tool that drives logged-in sessions receives cookies and proxy credentials, so it is fair to ask what it does with them. For antibrow:
The kernel is a closed-source Chromium build - that is the tradeoff for the spoofing living in C++ rather than in an injectable script - so verify behaviour rather than take it on faith:
python -m antibrow info # kernels, profiles, license state, cache dir
browser.plan.redacted_args() # exact kernel command line, secrets masked - safe to paste in a bug report
Point it at a proxy whose logs you can read, or at a local MITM proxy, and watch what leaves the machine during a launch. Pin the SDK version and check the published hash (npm view [email protected] dist.integrity) so the code you audited is the code that runs. If a deployment must not phone home at all, this is the wrong tool: license verification is compiled into the kernel and there is no offline mode.
Worth stating plainly, because a clean check list invites the wrong conclusion:
If every check passes and something still looks wrong, the cause is in this list, not in the browser layer.
Intended: verifying isolation between identities you own; running client accounts with the account holder's authorization; building QA fixtures that emulate distinct devices; testing your own anti-fraud and correlation logic; auditing what a browser runtime does with your credentials.
Out of scope, and not supported: accessing any system without authorization; logging into accounts that are not yours; credential stuffing or account takeover; creating fake accounts, reviews or engagement; circumventing an authentication, payment or authorization control; scraping personal data in violation of applicable law; working around a platform's enforcement decision.
Complying with the terms of the platforms being used, and with applicable law, is the operator's responsibility. Report abuse or a security issue via the contact at https://antibrow.com.
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 canva
---name: multi-account-isolationdescription: Verify that browser profiles are actually isolated from one another instead of assuming it - confirm each…---# multi-account-isolation/SKILL.mdÜbersicht
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.
FAQ
Laden Sie multi-account-isolation/SKILL.md vom Herausgeber herunter oder kopieren Sie den Pfad und öffnen Sie das Repository. PlugMCP listet den Skill und hostet die Datei nicht.
Der Herausgeber pflegt es unter https://github.com/antibrow/anti-detect-browser-skills.
Claude, Cursor, Codex und Grok Build können eine SKILL.md lesen, die Sie aus dem Repository des Herausgebers hinzufügen. Grok Bot installiert sie, wenn Sie den Link zum GitHub-Ordner des Skills in einem Chat senden.
| 10 | Whole-stack coherence | whoer.net, pixelscan.net | IP, timezone and locale disagree at a glance |
| 11 | Consistency rules in CI | npx liarjs (liarjs.dev) | Any of ~40 open-source cross-layer rules fail - this is the one that runs unattended |