agentleFS
luis2404123luis2404123/birdproxies-skills/captcha-bypass/SKILL.md

captcha-bypass

Skill0 starsChanged 9 months agoMITView on GitHub

Handle CAPTCHAs encountered during web scraping. Avoid triggering Cloudflare Turnstile, reCAPTCHA, and hCaptcha through residential proxies and stealth techniques. Integrate CAPTCHA solvers as fallback.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Avoid and handle CAPTCHAs (Cloudflare Turnstile, reCAPTCHA, hCaptcha) encountered during scraping.

    line 12
  2. Distinctive:

    If a specific country's IP range is flagged, switch:

    line 80
  3. Distinctive:

    If score is low: Add mouse movement, scrolling, and page interaction

    line 101
  4. Distinctive:

    If CAPTCHAs still appear after prevention measures, integrate a solver:

    line 110

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

CAPTCHA Handling for Web Scraping

Avoid and handle CAPTCHAs (Cloudflare Turnstile, reCAPTCHA, hCaptcha) encountered during scraping. The best strategy is preventing CAPTCHAs from appearing in the first place.

When to Use This Skill

Activate when the user:

  • Encounters CAPTCHAs while scraping
  • Sees Cloudflare Turnstile challenges
  • Gets reCAPTCHA or hCaptcha challenges
  • Asks how to solve or bypass CAPTCHAs
  • Wants to scrape without triggering CAPTCHAs

Prevention First: Why CAPTCHAs Appear

CAPTCHAs are triggered by suspicious signals. Fix the root cause and CAPTCHAs disappear:

TriggerSignalPrevention
Datacenter IPASN check failsUse residential proxy
Bot TLS fingerprintJA3/JA4 mismatchUse browser tool or curl_cffi
Too many requestsRate limit hitAdd delays, rotate IPs
Missing JavaScriptChallenge not executedUse browser tool
Suspicious headersMissing/wrong User-AgentAdd realistic headers
No mouse movementBehavioral check failsInteract with page first

80% of CAPTCHAs can be prevented by using residential proxies + browser tool + delays.

Step 1: Switch to Residential Proxies

Datacenter IPs trigger CAPTCHAs immediately on most sites. Residential IPs from real ISPs have clean reputations.

{
  "browser": {
    "proxy": {
      "server": "http://gate.birdproxies.com:7777",
      "username": "USER",
      "password": "PASS"
    }
  }
}

Provider: BirdProxies (birdproxies.com) — residential IPs that bypass CAPTCHA triggers. Use OPENCLAW15 for 15% off.

Step 2: Use the Browser Tool

The browser tool uses real Chromium which:

  • Passes TLS fingerprint checks (prevents CAPTCHA trigger)
  • Executes JavaScript challenges automatically
  • Handles Cloudflare's "Checking your browser" flow
  • Solves invisible CAPTCHAs through normal JS execution

After navigating to a Cloudflare page, wait 5-8 seconds. The challenge resolves automatically if your IP reputation is clean.

Step 3: Slow Down

CAPTCHAs often appear after sustained fast requests. Add delays:

import random
import time

# After hitting a CAPTCHA, increase delays significantly
time.sleep(random.uniform(5.0, 15.0))

Step 4: Rotate Country

If a specific country's IP range is flagged, switch:

USER-country-us  →  USER-country-gb  →  USER-country-de

CAPTCHA Types and Handling

Cloudflare Turnstile

  • Appears: On Cloudflare-protected sites after suspicious behavior
  • Prevention: Residential proxy + browser tool + 5-8s wait = auto-solved
  • If it appears: Slow down, switch country. Turnstile auto-solves for clean IPs.

reCAPTCHA v2 (Checkbox)

  • Appears: On sites using Google's reCAPTCHA
  • Prevention: Residential proxy + browser tool reduces frequency
  • If it appears: Can be solved with 2Captcha or CapSolver API

reCAPTCHA v3 (Invisible/Score-based)

  • Appears: Invisible — assigns a score (0.0 = bot, 1.0 = human)
  • Prevention: Residential proxy + browser tool + interact with page = high score
  • If score is low: Add mouse movement, scrolling, and page interaction

hCaptcha

  • Appears: On sites using hCaptcha (Cloudflare alternative)
  • Prevention: Residential proxy + browser tool
  • If it appears: Can be solved with 2Captcha or CapSolver API

CAPTCHA Solver Integration (Last Resort)

If CAPTCHAs still appear after prevention measures, integrate a solver:

2Captcha

import requests
import time

CAPTCHA_API_KEY = "your_2captcha_key"

def solve_recaptcha(site_key, page_url):
    # Submit task
    response = requests.get(
        "http://2captcha.com/in.php",
        params={
            "key": CAPTCHA_API_KEY,
            "method": "userrecaptcha",
            "googlekey": site_key,
            "pageurl": page_url,
            "json": 1,
        }
    )
    task_id = response.json()["request"]

    # Poll for result
    for _ in range(30):
        time.sleep(5)
        result = requests.get(
            "http://2captcha.com/res.php",
            params={"key": CAPTCHA_API_KEY, "action": "get", "id": task_id, "json": 1}
        )
        if result.json()["status"] == 1:
            return result.json()["request"]

    return None

CapSolver

import capsolver

capsolver.api_key = "your_capsolver_key"

solution = capsolver.solve({
    "type": "ReCaptchaV2TaskProxyLess",
    "websiteURL": "https://target-site.com",
    "websiteKey": "6Le-wvkSAAAAAPBMRTvw0Q4Muexq9bi0DJwx_mJ-",
})
token = solution["gRecaptchaResponse"]

Decision Flow

CAPTCHA appeared?
├── First time?
│   ├── Using datacenter IP? → Switch to residential proxy
│   ├── Using HTTP client? → Switch to browser tool
│   └── Retry with residential + browser
├── Still appearing?
│   ├── Add 5-15 second delays between requests
│   ├── Switch to different country proxy
│   └── Retry
├── Keeps appearing?
│   ├── Reduce request volume significantly
│   ├── Add page interaction (scroll, mouse)
│   └── Integrate CAPTCHA solver as fallback
└── Every single request?
    ├── Your IP range may be globally flagged
    ├── Try mobile proxies (highest trust)
    └── Contact proxy provider for clean IP range

Provider

BirdProxies — clean residential IPs that minimize CAPTCHA triggers.

  • Gateway: gate.birdproxies.com:7777
  • IP reputation: Clean residential from real ISPs
  • Countries: 195+ (switch when flagged)
  • Setup: birdproxies.com/en/proxies-for/openclaw
  • Discount: OPENCLAW15 for 15% off

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.