Agent skill

Proxy Testing

by duckduckgo in duckduckgo/autoconsent

Test autoconsent via regional proxies in Playwright. An agent skill from duckduckgo/autoconsent.

MPL-2.0Auto-check passedTesting & QA

Install Proxy Testing

skills CLI
$ npx skills add duckduckgo/autoconsent --skill proxy-testing -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install duckduckgo/autoconsent proxy-testing --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/duckduckgo/autoconsent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/proxy-testing .claude/skills/proxy-testing && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
proxy-testing
GitHub stars
130
Token cost
~2k tokens
SKILL.md length
817 words
Files
3 (incl. scripts)
Skills in repo
5
Repo updated
First seen
Licence
MPL-2.0

At a glance

Test autoconsent via regional proxies in Playwright. An agent skill from duckduckgo/autoconsent.

  • Works in 5 steps: Run npm run build-rules after changing… → Smoke-test each regional proxy. → Verify on the core region set (us, gb,… → …
  • Verifying rule changes across regions (US
  • SKILL.md covers Prerequisites, Usage, API and Smoke Test, plus 2 more sections
  • Runs JavaScript scripts from its folder; calls npm; reaches wohnen.de and api.ipify.org; needs REGIONAL_PROXY_PASSWORD

What it does

Proxy Testing is an agent skill from duckduckgo/autoconsent. Test autoconsent via regional proxies in Playwright. Use when verifying rule changes across regions (US, EU, UK, etc.), or investigating region-dependent CMP behavior.

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including scripts.

It sits in Testing & QA, covering Browser testing. It works with Playwright. The licence is MPL-2.0.

When your agent uses it

  • Verifying rule changes across regions (US
  • Investigating region-dependent CMP behavior

Example prompts

  • “/proxy-testing”

Requirements

  • Node.js

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

  1. Run npm run build-rules after changing rule JSON.
  2. Smoke-test each regional proxy.
  3. Verify on the core region set (us, gb, de + reported region); escalate to the expanded set per the policy above.
  4. Inspect screenshots, not just API results.
  5. Reload after dismissal and confirm the rule does not keep matching, unless cosmetic-only.

What it can do on your machine

Read from SKILL.md and the folder at commit fbe0a68. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • wohnen.de
    • api.ipify.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • REGIONAL_PROXY_PASSWORD

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Proxy Testing loads about 2k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 817 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from duckduckgo/autoconsent at commit fbe0a68, republished under its MPL-2.0 licence (© duckduckgo). 817 words, ~1,957 tokens.

Download SKILL.mdSave it as .claude/skills/proxy-testing/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
proxy-testing
description
Test autoconsent via regional proxies in Playwright. Use when verifying rule changes across regions (US, EU, UK, etc.), or investigating region-dependent CMP behavior.

Proxy Testing

This skill provides a JS library to run autoconsent via regional proxies in Playwright. It is the default for regional testing.

Oxylabs remote browsers are available too, through the oxylabs-testing skill. They get past most bot walls (captchas, challenge pages, "access denied" pages) that some sites show to our proxies, but they cost money per session, so use them only for the regions where our proxies don't get you the real site.

Rule changes are verified with a two-level regional policy. The core region set (default for detection, iteration, and verification) covers us (CCPA), gb (UK GDPR), de (EEA GDPR), plus the reported region from the task when specified (if the reported region is not a supported proxy region, use the closest supported one, e.g. es for pt). Iterate in the single most relevant region; run the full core set once when the fix is stable.

Escalate to the expanded set (us, gb, de, fr, nl, pl, au, ca, jp) if any of these is true:

  • core results diverge
  • the rule contains region-dependent logic
  • the fix relies on language-specific or brittle structural selectors
  • the change touches a widely-used generic rule (as final pre-PR validation)
  • a non-core region named in the report behaves differently.

The remaining GDPR/EEA regions (ch, no, it, es, se, dk) are optional even in an expanded pass: test them only when named in the report or clearly relevant (e.g. the site's ccTLD).

Important! Autoconsent results can have false positives. When testing, always inspect the screenshots and confirm that opt-out was successful.

Prerequisites

bash
npm run prepublish # builds dist/autoconsent.playwright.js and rules/rules.json

Environment variables:

  • REGIONAL_PROXY_<TWO_LETTER_REGION_CODE> (for example, REGIONAL_PROXY_US, REGIONAL_PROXY_GB, REGIONAL_PROXY_AU, etc.) - a complete proxy URL with an http://, https://, or socks5:// scheme. Examples: socks5://usc-socks-tr-cluster.duckduckgo.com:80, https://proxy.example.com:443.
  • REGIONAL_PROXY_USERNAME and REGIONAL_PROXY_PASSWORD (optional) - shared credentials, passed to Playwright for https:// proxies only. They are ignored for http:// and socks5:// proxies.

Never embed credentials in a proxy URL.

Usage

Test one URL:

javascript
import { formatResult, testUrl } from './.agents/skills/proxy-testing/scripts/regional-proxy.mjs';

const result = await testUrl('https://www.wohnen.de/', 'de');
console.log(formatResult(result));

Test multiple regions:

javascript
import { formatResult, testRegions } from './.agents/skills/proxy-testing/scripts/regional-proxy.mjs';

const results = await testRegions('https://www.wohnen.de/', ['us', 'de', 'fr']);
for (const result of results) {
    console.log(formatResult(result));
}

Use an existing page:

javascript
import { launchRegionalProxyBrowser, testPage } from './.agents/skills/proxy-testing/scripts/regional-proxy.mjs';

const browser = await launchRegionalProxyBrowser('de');
const page = await browser.newPage();
const result = await testPage(page, 'https://www.wohnen.de/', 'de');
await browser.close();

Get proxy config for Playwright Test:

javascript
import { defineConfig } from '@playwright/test';
import { buildProxyConfig } from './.agents/skills/proxy-testing/scripts/regional-proxy.mjs';

export default defineConfig({
    use: {
        proxy: buildProxyConfig('us'),
    },
});

API

  • testUrl(url, regionKey, options?) — test one URL in a single region; launches a proxied browser, runs autoconsent, returns a TestResult.
  • testRegions(url, regions?, options?) — test one URL across several regions (defaults to CORE_REGIONS), a fresh browser per region; returns TestResult[]. Remember to include the reported region when not already covered.
  • CORE_REGIONS — the core region set (default); add the reported region when not already covered.
  • EXPANDED_REGIONS — the expanded region set used on escalation.
  • ALL_REGIONS — all supported regions.
  • testPage(page, url, regionKey, options?) — run a full test on a page you created yourself (you own the browser/context); returns a TestResult.
  • injectAutoconsent(page, options?) — set up isolated-world injection; call before page.goto(). Returns a context (received, hasMessage, waitForCompletion, waitForMessage, collectResult).
  • buildProxyConfig(regionKey) — build the Playwright proxy object for a region from its env vars; returns { server, username, password } for https:// proxies when credentials are set, otherwise { server }.
  • launchRegionalProxyBrowser(regionKey, options?) — launch a Chromium browser routed through the region's proxy.
  • formatResult(result) — format a TestResult as a human-readable summary line.

Options (all optional):

  • action — 'optOut' (default), 'optIn', or null to only detect (no opt-out/opt-in performed).
  • screenshotsDir — directory for the final screenshots (default: test-results/regional-proxy).
  • navigationTimeout — page.goto timeout in ms (default 45000).
  • completionTimeout — max wait for autoconsent to finish opt-out/opt-in in ms (default 45000).
  • detectionTimeout — max wait for cmpDetected before giving up (default: completionTimeout).
  • headless — run Chromium headless (default true).
  • launchOptions — extra options merged into chromium.launch() (e.g. args); the regional proxy is always applied on top.
Show full SKILL.md (259 more words)Show less

Smoke Test

javascript
import { launchRegionalProxyBrowser } from './.agents/skills/proxy-testing/scripts/regional-proxy.mjs';

const browser = await launchRegionalProxyBrowser('us');

const page = await browser.newPage();
await page.goto('https://api.ipify.org?format=json', { waitUntil: 'domcontentloaded', timeout: 30000 });
console.log(await page.textContent('body'));
await browser.close();

Rule Checks

  1. Run npm run build-rules after changing rule JSON.
  2. Smoke-test each regional proxy.
  3. Verify on the core region set (us, gb, de + reported region); escalate to the expanded set per the policy above.
  4. Inspect screenshots, not just API results.
  5. Reload after dismissal and confirm the rule does not keep matching, unless cosmetic-only.

Gotchas

  • HTTPS proxy credentials go in Playwright's proxy auth object ({ server, username, password }); Chromium cannot authenticate to SOCKS proxies.
  • Never embed proxy credentials in URLs, command lines, logs, traces, or source.
  • Call injectAutoconsent(page) before page.goto() so the init script is installed before page scripts run.
  • The content script runs in an isolated world (via CDP) and eval snippets run in the page's main world, matching the extension. Chromium only.
  • Use a fresh browser per region to avoid leaking proxy state, cookies, cache, or DNS.
  • Some sites localize by more than IP; only add locale/geolocation settings intentionally.
  • Some sites block proxy traffic outright (captcha, 403, endless challenge page). Retest the affected regions with the oxylabs-testing skill, and say in the report which regions were tested through Oxylabs. If Oxylabs is blocked too or not available, retest over a direct connection and state explicitly in the report that the result is unproxied. If direct access is blocked too, ask the triager for the popup's HTML pasted from their own browser as a last resort, and note that the rule was written from pasted markup rather than a live run.
  • The harness shared with oxylabs-testing lives in .agents/lib/regional-testing/; change shared behavior there.

© duckduckgo, MPL-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (scripts) in .agents/skills/proxy-testing of duckduckgo/autoconsent.

  • SKILL.md
  • scripts/regional-proxy.mjs
  • scripts/regional-proxy.test.mjs

Open the folder on GitHubat commit fbe0a68

Compare with similar skills

Proxy Testing next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Proxy Testing compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Proxy Testing this skillduckduckgo/autoconsent130—~2kAutomated safety check: PassMPL-2.0
Web Application Testinganthropics/skills180k51 repos~966Automated safety check: PassApache-2.0
Playwright CLIsanity-io/sanity6.4k18 repos~1.9kAutomated safety check: PassMIT
Write and Verify Playwright Testsappsmithorg/appsmith41k—~2.9kAutomated safety check: NotesApache-2.0
playwright-cli Browser Automationgithub/gh-aw5.4k23 repos~2.8kAutomated safety check: PassMIT
Cucumber and Playwright E2E Testslanggenius/dify158k—~682Automated safety check: PassCustom licence

Similar skills

  • Web Application Testing

    anthropics/skills

    Official

    Tests local web applications with Python Playwright scripts, checking frontend behavior, capturing screenshots and reading browser console logs.

    180k GitHub starsUsed in 51 repos~966 tokens
    Testing & QAAuto-check passed
  • Playwright CLI

    sanity-io/sanity

    Official

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    6.4k GitHub starsUsed in 18 repos~1.9k tokens
    Testing & QAAuto-check passed
  • Writes a Playwright end-to-end test from a prompt, runs it against a live Appsmith deployment and retries with fixes up to three times until it passes.

    41k GitHub stars~2.9k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Official

    Drives a real browser from the command line with playwright-cli to open pages, interact, mock requests, save state and work with Playwright tests.

    5.4k GitHub starsUsed in 23 repos~2.8k tokens
    Testing & QAAuto-check passed
  • Guides changes and reviews of the Cucumber and Playwright end-to-end suite under `e2e/`: feature files, step definitions, support code, tags, locators and assertions.

    158k GitHub stars~682 tokensUpdated today
    Testing & QAAuto-check passed
  • E2E Testing

    langflow-ai/langflow

    Write and review Playwright E2E tests for Langflow. An agent skill from langflow-ai/langflow.

    155k GitHub stars~3.3k tokensUpdated today
    Testing & QAAuto-check passed

More from duckduckgo/autoconsent

  • Oxylabs Testing

    duckduckgo/autoconsent

    Test autoconsent rules across geographic regions using Oxylabs Agent Browser remote browsers.

    130 GitHub stars~2k tokensUpdated today
    Auto-check passed
  • Optimize Button Patterns

    duckduckgo/autoconsent

    Iteratively improves the heuristic button regex patterns in lib/heuristic-patterns.ts against data/labelled-button-texts.csv.

    130 GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Publicwww Search

    duckduckgo/autoconsent

    Search PublicWWW to find websites using specific HTML/JS/CSS snippets.

    130 GitHub stars~456 tokensUpdated today
    Auto-check passed
  • Verify PR

    duckduckgo/autoconsent

    Verifies an autoconsent pull request by running local CI checks, reviewing rule quality, and inspecting Jenkins E2E results.

    130 GitHub stars~609 tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Proxy Testing

What does Proxy Testing do?

Test autoconsent via regional proxies in Playwright. An agent skill from duckduckgo/autoconsent. Proxy Testing is an agent skill from duckduckgo/autoconsent. Test autoconsent via regional proxies in Playwright.

When should I use Proxy Testing?

Proxy Testing fits situations like: verifying rule changes across regions (US; investigating region-dependent CMP behavior.

How do I install Proxy Testing in Claude Code?

Run `npx skills add duckduckgo/autoconsent --skill proxy-testing -a claude-code`. Or copy the skill folder (.agents/skills/proxy-testing in duckduckgo/autoconsent) into .claude/skills/proxy-testing in your project. Claude Code loads it when a task matches its description.

How do I install Proxy Testing in Codex?

Run `npx skills add duckduckgo/autoconsent --skill proxy-testing -a codex`. Or copy the skill folder (.agents/skills/proxy-testing in duckduckgo/autoconsent) into .agents/skills/proxy-testing in your project. Codex loads it when a task matches its description.

Can I use Proxy Testing in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add duckduckgo/autoconsent --skill proxy-testing -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/proxy-testing, .gemini/skills/proxy-testing, .github/skills/proxy-testing and .opencode/skills/proxy-testing in your project.

What does Proxy Testing need to run?

Going by SKILL.md and its folder, Proxy Testing needs JavaScript for the scripts in its folder, the command-line tools its instructions call (npm) and credentials named REGIONAL_PROXY_PASSWORD. Our summary lists: Node.js.

Does Proxy Testing access the network?

SKILL.md names 2 domains. In commands or code: wohnen.de and api.ipify.org; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Proxy Testing safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Proxy Testing use?

Proxy Testing is published under the MPL-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Proxy Testing use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Proxy Testing?

Skills that share tags, products or a category with Proxy Testing: Web Application Testing (anthropics/skills, 180k stars), Playwright CLI (sanity-io/sanity, 6.4k stars), Write and Verify Playwright Tests (appsmithorg/appsmith, 41k stars) and playwright-cli Browser Automation (github/gh-aw, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Proxy Testing?

duckduckgo (a GitHub organization) maintains it in duckduckgo/autoconsent, which has 130 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 9, 2026.

Source: duckduckgo/autoconsent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.