Anti-Detect Browser
Drive Chromium with a kernel-level real-device fingerprint via standard Playwright APIs — persistent isolated profiles, per-profile proxies
- What
- Drive Chromium with a kernel-level real-device fingerprint via standard Playwright APIs — persistent isolated profiles, per-profile proxies
- Cost
- Free
- Needs
- an antibrow.com account with API key (paid plans); Node 18+ or Python 3.9–3.13; Playwright; proxies if geo-specific exits are needed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an SDK skill for launching Chromium with a real-device fingerprint applied inside the kernel (canvas, WebGL, audio, fonts, navigator, TLS ClientHello all coherent) through standard Playwright APIs, with one persistent isolated profile per identity and per-profile proxies whose exit IP sets timezone and WebRTC. Includes npm (`anti-detect-browser`) and PyPI (`antibrow`) packages. By @antibrow, listed here with credit to its creator. Honest caveats: dual use — powerful for QA, ad verification, and testing your own bot detection, but it is fingerprint-evasion technology; the repo carries an "Authorized use only" section (your own accounts, your own sites, public data, lawful use). Requires an antibrow.com account/API key. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an antibrow.com account with API key (paid plans); Node 18+ or Python 3.9–3.13; Playwright; proxies if geo-specific exits are needed Install "Anti-Detect Browser" for me. Drive Chromium with a kernel-level real-device fingerprint via standard Playwright APIs — persistent isolated profiles, per-profile proxies Repository: https://github.com/antibrow/anti-detect-browser-skills 1. Fetch the SKILL.md file for the antibrow-anti-detect-browser 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-anti-detect-browser". 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.