Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add interfluve-wav/auto-captcha-solver --skill hermes-skillgit clone --depth 1 https://github.com/interfluve-wav/auto-captcha-solverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/interfluve-wav/auto-captcha-solver/hermes-skill)<a href="https://agentmods.dev/skills/interfluve-wav/auto-captcha-solver/hermes-skill"><img src="https://agentmods.dev/badge/skills/interfluve-wav/auto-captcha-solver/hermes-skill/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/interfluve-wav/auto-captcha-solver/hermes-skill"><img src="https://agentmods.dev/badge/skills/interfluve-wav/auto-captcha-solver/hermes-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00057 | $0.01476 |
| Opus 5.5 | $0.00023 | $0.00590 |
| Sonnet 5.5 | $0.00011 | $0.00295 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
auto-captcha-solver scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-Captcha
Auto-detect and solve captchas during Playwright browser automation using the NopeCHA API.
When to Use
- Browser automation hits a captcha wall
- Web scraping tasks need captcha bypass
- Automated testing against captcha-protected sites
- Any Playwright script that might encounter hCaptcha or reCAPTCHA v2
Prerequisites
NOPECHA_API_KEYenv var set (get free credits at https://nopecha.com)- Python
requestsandplaywrightinstalled - Playwright browser installed (
python -m playwright install chromium)
Quick Start
from auto_captcha_solver import CaptchaSolver
solver = CaptchaSolver(api_key="your-key")
# Auto-detect + solve + inject (one-liner)
results = solver.auto_solve(page)
Full API
Detect
captchas = solver.detect(page)
# Returns: [{"type": "hcaptcha"|"recaptcha2", "sitekey": "...", "url": "...", "frame": ...}]
Solve
result = solver.solve("hcaptcha", sitekey, page_url)
# Returns: CaptchaResult(success=True, token="...", attempts=5, elapsed_sec=38.0)
Inject
solver.inject(page, "hcaptcha", token)
# Injects token into page's captcha callback
Auto (detect + solve + inject)
results = solver.auto_solve(page)
for r in results:
print(f"{r.captcha_type}: {'OK' if r.success else r.error}")
SmartPage (transparent wrapper)
from auto_captcha_solver import smart_page
with smart_page(api_key="your-key") as page:
page.goto("https://protected-site.com")
page.fill("#email", "[email protected]")
page.click("#submit") # captcha auto-solved after each action
Supported Captcha Types
| Type | API Endpoint | Status |
|---|---|---|
| hCaptcha (checkbox) | /v1/token/hcaptcha |
Working |
| hCaptcha (enterprise) | /v1/token/hcaptcha |
Working |
| reCAPTCHA v2 | /v1/token/recaptcha2 |
Works but queue can be slow |
| reCAPTCHA v3 | /v1/token/recaptcha3 |
Working (needs data.action) |
| Cloudflare Turnstile | /v1/token/turnstile |
Working with a proxy — proxy is Required in NopeCHA's schema for this endpoint (solver exit IP must match browser IP); check_proxy_egress() / CLI proxy-check verify first. Error 10 bodies carry a diagnostic type field, now surfaced in the error string. |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago Changed · +35 lines 5f79506f60a3
- 1mo ago First seen · 123 lines · 57 tokens per session scan A 34735ee92622
auto-captcha-solver is a skill published in the GitHub repository interfluve-wav/auto-captcha-solver (10 stars, last pushed 24d ago), licensed MIT. It adds 57 tokens to every session and 1,476 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gem-pw
Browser-automated Gemini Gem CLI (CDP-first) — chat, CRUD, image gen, deep research, --collab surgical-diff review. No API key.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
opencli-adapter-author
Build or improve an OpenCLI JS adapter using observed site behavior, existing adapters and browser API evidence. For ad-hoc browser interaction, see opencli-browser.
opencli-browser
Drive Chrome with OpenCLI to inspect pages, interact with logged-in sites, capture API evidence, and manage native tabs, groups and windows. For reusable adapters, see opencli-adapter-author.
webcmd-browser
Use when a live browser task requires Playwright interaction, authenticated handoff, visible UI verification, or ad-hoc page inspection.
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.