Multi-Account Isolation
Verify browser profiles are actually isolated — timezone vs exit IP, WebRTC leaks, fingerprint consistency across relaunches
- What
- Verify browser profiles are actually isolated — timezone vs exit IP, WebRTC leaks, fingerprint consistency across relaunches
- Cost
- Free
- Needs
- the antibrow SDK installed and profiles/proxies set up via the anti-detect-browser skill — verification only, no dependencies beyond that
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a verification checklist skill for browser profile isolation: confirm each profile's timezone agrees with its exit IP, that WebRTC exposes only the proxy, that canvas/WebGL hashes stay identical across relaunches of one profile, and that no two profiles share a persona, cookie jar, or address. Points to detection suites (CreepJS, whoer, browserleaks, pixelscan, liarjs) to measure against. By @antibrow, listed here with credit to its creator. Honest caveats: dual use — the repo carries an "Authorized use only" section (identities you own or are authorized to operate); passing every check proves browser-layer consistency only, never that a site will treat two profiles as unrelated. Requires the antibrow SDK. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the antibrow SDK installed and profiles/proxies set up via the anti-detect-browser skill — verification only, no dependencies beyond that Install "Multi-Account Isolation" for me. Verify browser profiles are actually isolated — timezone vs exit IP, WebRTC leaks, fingerprint consistency across relaunches Repository: https://github.com/antibrow/anti-detect-browser-skills 1. Fetch the SKILL.md file for the antibrow-multi-account-isolation skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "antibrow-multi-account-isolation". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.