Individual skill
anti-detect-browser
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.
anti-detect-browser/SKILL.md
Source commit b800e3a54d8d4f93ae5ee23c59d13b43df5d4462
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 21
- Repository last updated
- Aug 28, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- gemini-cli-extension Repository topic
- mcp Repository topic
- testing Derived category
- testing-browser Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesSKILL.mdcore · 39,236 bytesreferences/android-profiles.mddoc · 4,817 bytesreferences/rest-api-and-docker.mddoc · 2,920 bytes
Read excerpt
# Anti-Detect Browser SDK
Launch Chromium instances with real-device fingerprints via standard Playwright APIs. Every profile carries one coherent, real-device identity that is frozen at creation and replayed byte-for-byte on every later launch.
- npm package: `anti-detect-browser` (Node >= 18)
- PyPI package: `antibrow` (Python 3.9 - 3.13)
- Dashboard: `https://antibrow.com`
- REST API base: `https://antibrow.com/api/v1/`
- Documentation: `https://antibrow.com/docs`
> **Authorized use only.** This is for automating systems you own or are permitted to use: your own accounts, your own site's bot detection and anti-fraud stack, publicly available data, and region-specific views of your own ads and pricing. Do not use it to access systems without authorization, to log into accounts that are not yours, to create fake accounts or engagement, or to work around a platform's enforcement decision. Respect each site's terms, `robots.txt` and rate limits, and applicable law - see [Acceptable use](#acceptable-use).
**What this does not claim.** A coherent real-device fingerprint removes the *contradictions* a synthetic browser leaves behind. It is not a guaranteed pass against enterprise bot managers, which also score network reputation, request patterns, behaviour and account history - none of which a fingerprint touches. Measure with the suites listed under [What detection actually tests](#what-detection-actually-tests) rather than assuming.