Skip to content

johnalbertini14-glitch/openclaw-skills / skills/0xclanky/captcha-relay

captcha-relay

Flagged

Human-in-the-loop CAPTCHA solving with two modes: screenshot (default, zero infrastructure) and token relay (requires network access). Screenshot mode captures the page with a grid overlay, sends it to the human, and injects clicks based on their reply. Token relay mode detects CAPTCHA type + sitekey, serves the real widget on a relay page for native solving, and injects the token via CDP.

FileKindSize
ARCHITECTURE.mdmarkdown4.2 KB
README.mdmarkdown4.0 KB
SKILL.mdskill md3.6 KB
TAILSCALE.mdmarkdown3.0 KB
_meta.jsonconfig458 B
browser-relay-cli.jsscript981 B
fallback/screenshot.jsscript5.2 KB
index.jsscript5.4 KB
lib/browser-relay.jsscript7.9 KB
lib/cdp.jsscript2.8 KB
lib/detect.jsscript2.8 KB
lib/inject.jsscript4.5 KB
lib/server.jsscript2.6 KB
lib/templates/browser-relay.htmlother7.5 KB
lib/templates/hcaptcha.htmlother1.8 KB
lib/templates/recaptcha-v2.htmlother1.9 KB
lib/templates/turnstile.htmlother1.8 KB
lib/tunnel.jsscript4.2 KB
package-lock.jsonmanifest17.2 KB
package.jsonmanifest443 B

TAILSCALE.md

View on GitHub
# Tailscale Setup for CAPTCHA Relay

Tailscale creates a private mesh VPN (Tailnet) between your devices. With it, the relay server is directly accessible from your phone — no tunneling, no splash pages, no TLS issues.

## Why Tailscale?

| Approach | Pros | Cons |
|----------|------|------|
| localtunnel | Free, no setup | Splash page, unreliable, public URL |
| cloudflared | Fast | Heavy binary, resource-hungry |
| **Tailscale** | Always-on, private, fast, no splash | Requires install on both devices |

## Setup

### 1. Server (Ubuntu Linux)

```bash
# Install
curl -fsSL https://tailscale.com/install.sh | sh

# Start and authenticate
sudo tailscale up

# Note your Tailscale IP
tailscale ip -4
# e.g., 100.x.y.z
```

The machine gets a stable `100.x.y.z` Tailscale IP on your private Tailnet.

### 2. Phone (iOS/Android)

1. Install Tailscale from App Store / Play Store
2. Sign in with the same account (Google, Microsoft, GitHub, etc.)
3. Enable the VPN toggle
4. Both devices are now on the same Tailnet

### 3. Integration with captcha-relay

Run with `--no-tunnel` and use the Tailscale IP:

```bash
# On the server
TAILSCALE_IP=$(tailscale ip -4)
node index.js --no-tunnel
# The relay URL will be http://100.x.y.z:PORT
```

Or in module mode:

```js
const result = await solveCaptcha({
  useTunnel: false,  // no tunnel needed
});
// result.relayUrl will be http://<local-ip>:PORT
// With Tailscale, <local-ip> should resolve to the Tailscale IP
```

**Note**: The `getLocalIp()` function in tunnel.js returns the first non-internal IPv4 address. If Tailscale is active, you may want to explicitly use the `tailscale ip -4` output. A future enhancement could auto-detect the Tailscale interface (`tailscale0`).

### 4. MagicDNS (Optional)

Tailscale assigns human-readable names to devices:

```
http://clankys-house:PORT
```

Enable MagicDNS in the Tailscale admin console for this to work.

## Free Tier

Tailscale's free "Personal" plan includes:
- **Up to 3 users**
- **Up to 100 devices**
- All core features (MagicDNS, HTTPS, ACLs)
- No bandwidth limits
- No time limits

This is more than enough for personal use.

## Security

- Traffic is encrypted end-to-end (WireGuard)
- The relay server is only accessible to devices on your Tailnet
- No public URLs — unlike localtunnel/cloudflared, nothing is exposed to the internet
- This is actually more secure than the tunnel approaches

## Pros/Cons Summary

**Pros:**
- Always-on — no need to start/stop tunnels per CAPTCHA
- No splash pages or interstitials
- Private and encrypted
- Reliable — no dependency on third-party tunnel services
- Fast — direct WireGuard connection
- Free for personal use

**Cons:**
- One-time setup required on each device
- Adds a background service/VPN on the phone
- Need same auth account on both devices
- If Tailscale service is down (rare), no connectivity

## Recommendation

For development/testing: use localtunnel (zero setup).
For production/daily use: set up Tailscale once and forget about tunneling forever.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall