anti-detect-browser

antibrow/anti-detect-browser-skills · updated May 27, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/antibrow/anti-detect-browser-skills --skill anti-detect-browser
0 commentsdiscussion
summary

Launch Chromium instances with real-device fingerprints via standard Playwright APIs. Each browser gets a unique, consistent digital identity - undetectable by anti-bot systems.

skill.md

Anti-Detect Browser SDK

Launch Chromium instances with real-device fingerprints via standard Playwright APIs. Each browser gets a unique, consistent digital identity - undetectable by anti-bot systems.

  • npm package: anti-detect-browser
  • Dashboard: https://antibrow.com
  • REST API base: https://antibrow.com/api/v1/
  • Documentation: https://antibrow.com/docs

When to use

  • Multi-account management - Run dozens of social media, e-commerce, or ad accounts on the same machine without linking. Each browser profile has its own fingerprint, cookies, and storage.
  • Web scraping & data collection - Rotate fingerprints across scraping sessions to avoid detection and fingerprint-IP correlation bans.
  • Ad verification & competitive intelligence - View ads and content as different user profiles across regions and device types.
  • Social media automation - Manage multiple accounts with persistent profiles that survive browser restarts.
  • E-commerce operations - Operate multiple seller/buyer accounts with fully isolated browser environments.
  • AI agent browser control - Run as an MCP server so AI agents (Claude, GPT, etc.) can launch, navigate, and interact with anti-detect browsers through tool calls.
  • QA & cross-environment testing - Test how your site behaves under different browser fingerprints, screen sizes, and device configurations.

Quick start

npm install anti-detect-browser
import { AntiDetectBrowser } from 'anti-detect-browser'

// Get your API key at https://antibrow.com
const ab = new AntiDetectBrowser({ key: 'your-api-key' })

const { browser, page } = await ab.launch({
  fingerprint: { tags: ['Windows 10', 'Chrome'] },
  profile: 'my-account-01',
  proxy: 'http://user:pass@host:port',
})

// Standard Playwright API from here — zero learning curve
await page.goto('https://example.com')
await browser.close()

Core concepts

Profiles — persistent browser identities

A profile saves cookies, localStorage, and session data across launches. Same profile name = same stored state next time.

// First launch — fresh session
const { page } = await ab.launch({ profile: 'shop-01' })
await page.goto('https://shop.example.com/login')
// ... login ...
await browser.close()

// Later — session restored, already logged in
const { page: p2 } = await ab.launch({ profile: 'shop-01' })
await p2.goto('https://shop.example.com/dashboard') // no login needed

Fingerprints — real device data from the cloud

Each launch fetches a real fingerprint collected from actual devices. Over 30 categories (Canvas, WebGL, Audio, Fonts, WebRTC, WebGPU, etc.) with 500+ individual parameters.

// Windows Chrome, version 130+
await ab.launch({
  fingerprint: { tags: ['Windows 10', 'Chrome'], minBrowserVersion: 130 },
})

// Mac Safari
await ab.launch({
  fingerprint: { tags: ['Apple Mac', 'Safari'] },
})

// Mobile Android
await ab.launch({
  fingerprint: { tags: ['Android', 'Mobile', 'Chrome'] },
})

Available filter tags: Microsoft Windows, Apple Mac, Android, Linux, iPad, iPhone, Edge, Chrome, Safari, Firefox, Desktop, Mobile, Windows 7, Windows 8, Windows 10

Visual identification — tell windows apart at a glance

When running many browsers simultaneously, each window gets a floating label, title prefix, and unique theme color.

await ab.launch({
  profile: 'twitter-main',
  label: '@myhandle',       // floating label + window title
  color: '#e74c3c',         // unique window border color
})

Proxy integration

Route each browser through a different proxy for geo-targeting or IP rotation.

await ab.launch({
  proxy: 'socks5://user:[email protected]:1080',
  fingerprint: { tags: ['Windows 10', 'Chrome'] },
  profile: 'us-account',
})

Live View — watch headless browsers in real time

Monitor headless sessions from the https://antibrow.com dashboard. Useful for debugging AI agent actions or letting team members observe.

const { liveView } = await ab.launch({
  headless: true,
  liveView: true,
})

console.log('Watch live:', liveView.viewUrl)
// Share this URL — anyone with access can see the browser screen

Inject into existing Playwright setup

Already have Playwright scripts? Add fingerprints without changing your workflow.

import { chromium } from 'playwright'
import { applyFingerprint } from 'anti-detect-browser'

const browser = await chromium.launch()
const context = await browser.newContext()

await applyFingerprint(context, {
  key: 'your-api-key',
  fingerprint: { tags: ['Windows 10', 'Chrome'] },
  profile: 'my-profile',
})

const page = await context.newPage()
await page.goto('https://example.com')

MCP server mode — for AI agents

Run as an MCP server so AI agents can launch and control fingerprint browsers via tool calls.

{
  "mcpServers": {
    "anti-detect-browser": {
      "command": "npx",
      "args": ["anti-detect-browser", "--mcp"],
      "env": { "ANTI_DETECT_BROWSER_KEY": "your-api-key" }
    }
  }
}

Available tools:

Tool What it does
launch_browser Start a new fingerprint browser session
close_browser Close a running session
navigate Go to a URL
screenshot Capture the current screen
click / fill Interact with page elements
evaluate Run JavaScript on the page
get_content Extract text from the page or a specific element
start_live_view Stream the browser screen to https://antibrow.com dashboard
stop_live_view Stop live streaming
list_sessions List all running browser instances
list_profiles List all saved profiles

Workflow examples

Multi-account social media

const accounts = [
  { profile: 'twitter-1', label: '@brand_main', color: '#1DA1F2' },
  { profile: 'twitter-2', label: '@support', color: '#FF6B35' },
  { profile: 'twitter-3', label: '@personal', color: '#6C5CE7' },
]

for (const acct of accounts) {
how to use anti-detect-browser

How to use anti-detect-browser on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your development machine
  • Node.js version 16.0+ with npm package manager (verify with node --version)
  • Active project directory or workspace where you want to add anti-detect-browser
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/antibrow/anti-detect-browser-skills --skill anti-detect-browser

The skills CLI fetches anti-detect-browser from GitHub repository antibrow/anti-detect-browser-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/anti-detect-browser

Reload or restart Cursor to activate anti-detect-browser. Access the skill through slash commands (e.g., /anti-detect-browser) or your agent's skill management interface.

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases

User Story & Requirements Generation

Create detailed user stories, acceptance criteria, and feature specs

Example

Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios

Reduce spec writing time by 50%, ensure comprehensive coverage

Competitive Analysis

Research competitors, compare features, identify gaps

Example

Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities

Complete competitive research in 2 hours instead of 2 days

Roadmap Prioritization

Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs

Example

Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale

Make data-driven prioritization decisions faster

Stakeholder Communication

Draft PRDs, status updates, and stakeholder presentations

Example

Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement

Save 3-5 hours/week on communication overhead

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client
  • Access to product documentation and roadmap tools (Jira, Notion, etc.)
  • Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
  • Stakeholder contact information and communication channels

Time Estimate

30-60 minutes to see productivity improvements

Installation Steps

  1. 1.Install product management skill
  2. 2.Start with user story generation for known feature
  3. 3.Progress to competitive analysis: research 2-3 competitors
  4. 4.Use for roadmap prioritization: apply RICE/ICE scoring
  5. 5.Draft stakeholder communications and refine based on feedback
  6. 6.Build template library for recurring PM tasks
  7. 7.Share effective prompts with product team

Common Pitfalls

  • Not validating competitive research—verify facts before sharing
  • Accepting user stories without involving engineering team
  • Over-relying on frameworks without qualitative judgment
  • Not customizing outputs to company culture and communication style
  • Skipping stakeholder validation of generated requirements

Best Practices

✓ Do

  • +Validate research and competitive analysis with real data
  • +Collaborate with engineering when generating technical requirements
  • +Customize frameworks and templates to your company context
  • +Use skill for first drafts, refine with stakeholder input
  • +Document successful prompt patterns for PM tasks
  • +Combine AI efficiency with human judgment and intuition

✗ Don't

  • Don't publish competitive analysis without fact-checking
  • Don't finalize user stories without engineering review
  • Don't make prioritization decisions solely on AI scoring
  • Don't skip customer validation of generated requirements
  • Don't ignore company-specific context and culture

💡 Pro Tips

  • Provide context: company goals, constraints, customer feedback
  • Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
  • Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
  • Use skill for 70% generation + 30% customization to company needs

When to Use This

✓ Use When

Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.

✗ Avoid When

Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.

Learning Path

  1. 1Basic: user stories, feature specs, status updates
  2. 2Intermediate: competitive analysis, prioritization frameworks, PRDs
  3. 3Advanced: product strategy, go-to-market planning, OKR setting
  4. 4Expert: product vision, market positioning, business model innovation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.672 reviews
  • Amelia Sethi· Dec 16, 2024

    Registry listing for anti-detect-browser matched our evaluation — installs cleanly and behaves as described in the markdown.

  • Amelia Jackson· Dec 12, 2024

    anti-detect-browser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Ganesh Mohane· Dec 8, 2024

    anti-detect-browser is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • Alexander Park· Dec 8, 2024

    I recommend anti-detect-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sakshi Patil· Nov 27, 2024

    Keeps context tight: anti-detect-browser is the kind of skill you can hand to a new teammate without a long onboarding doc.

  • Charlotte Ndlovu· Nov 27, 2024

    anti-detect-browser fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • Advait Ndlovu· Nov 7, 2024

    anti-detect-browser reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • Arya Singh· Nov 3, 2024

    I recommend anti-detect-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Anaya Desai· Oct 26, 2024

    I recommend anti-detect-browser for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • Sophia Sharma· Oct 22, 2024

    anti-detect-browser reduced setup friction for our internal harness; good balance of opinion and flexibility.

showing 1-10 of 72

1 / 8