AgentGo Cloud Browser

v0.1.0

Automates browser interactions using AgentGo's distributed cloud browser cluster via playwright@1.51.0. Use when the user needs to navigate websites, interac...

0· 366·4 current·4 all-time
byPangolinfo & AgentGo@tammy-hash

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for tammy-hash/agentgo-browser.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "AgentGo Cloud Browser" (tammy-hash/agentgo-browser) from ClawHub.
Skill page: https://clawhub.ai/tammy-hash/agentgo-browser
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install agentgo-browser

ClawHub CLI

Package manager switcher

npx clawhub@latest install agentgo-browser
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
high confidence
!
Purpose & Capability
The SKILL.md content, reference files, and examples are consistent with the stated purpose (connecting to AgentGo via Playwright to automate browsers). However the registry metadata lists no required environment variables while the runtime instructions repeatedly require process.env.AGENTGO_API_KEY; this metadata/instruction mismatch is an incoherence that could lead to accidental misconfiguration or missing security controls. Also the skill teaches cookie injection and anti-detection tactics — technically within the automation purpose but sensitive in consequence.
Instruction Scope
Instructions stay within browser automation scope (connect to wss://app.browsers.live, use Playwright APIs, manage sessions). They also include explicit anti-detection strategies (mobile emulation, human-like typing, simulated scrolling) and step-by-step instructions for extracting and injecting session cookies (e.g., for X/Twitter). Those behaviors are coherent for a tool designed to automate human-like interactions, but they are powerful and can enable actions that bypass site protections or operate on someone else's account if cookies/credentials are mishandled.
Install Mechanism
This is an instruction-only skill (no install spec). It tells users to install a specific package (playwright@1.51.0). No arbitrary download URLs or extract steps are present. The requirement to use an exact older Playwright version is fragile and worth noting, but not an install-security red flag by itself.
!
Credentials
The runtime examples and helpers require AGENTGO_API_KEY (read from process.env), and the docs instruct storing session cookies locally (or in env/config). Yet the skill metadata declares no required environment variables or primary credential. This mismatch is concerning because sensitive credentials (API key and session cookies) are needed to operate and they are not documented in the metadata that the platform uses to surface permissions. The skill also instructs reading local config files (e.g., x_config.json), which involves handling secrets outside the declared requirements.
Persistence & Privilege
The skill does not request elevated platform privileges: always:false, no OS restrictions, and it does not describe modifying other skills or system-wide config. There is no evidence it attempts to persist beyond its normal use.
What to consider before installing
This skill appears to implement what it claims (cloud Playwright automation) but there are red flags you should consider before installing: - AGENTGO_API_KEY is required by the examples but is not declared in the skill metadata. Confirm with the publisher that the skill will request this credential and understand how/where you must provide it. - The references include explicit anti-detection techniques and instructions for extracting/injecting session cookies (e.g., X/Twitter auth_token and ct0). These are powerful and can be abused; never provide cookies or API keys for accounts you do not own, and avoid automating actions that violate a service's terms of use. - Trust the remote endpoint (wss://app.browsers.live and https://app.agentgo.live). Using this skill will route browsing through a third-party cloud provider — review their privacy/security policy and understand what data may be logged or visible to them (page URLs, contents, session cookies, screenshots, etc.). - Use least-privilege: create and use dedicated/test accounts and limited-scope API keys if possible. Do not store API keys or cookies in source control; follow the skill's own advice to keep them out of VCS and use secure storage. - Because the SKILL.md pins an exact Playwright version (1.51.0), run the automation in an isolated environment (container or VM) to avoid dependency conflicts and to limit impact if credentials are leaked. If you plan to proceed, ask the skill publisher to update the metadata to declare AGENTGO_API_KEY as a required credential and to document how cookies/credentials should be handled safely. If you need this skill to act autonomously, consider the additional risk that the automation could perform high-impact actions using the provided cookies/API key.

Like a lobster shell, security has layers — review code before you run it.

agentgovk97a3b7jd4gvyg6r6pv7ee1vcd82edzgautomationvk97a3b7jd4gvyg6r6pv7ee1vcd82edzgbrowservk97a3b7jd4gvyg6r6pv7ee1vcd82edzgcloudvk97a3b7jd4gvyg6r6pv7ee1vcd82edzgcrawlingvk97a3b7jd4gvyg6r6pv7ee1vcd82edzglatestvk97a3b7jd4gvyg6r6pv7ee1vcd82edzgplaywrightvk97a3b7jd4gvyg6r6pv7ee1vcd82edzgscrapingvk97a3b7jd4gvyg6r6pv7ee1vcd82edzgtestingvk97a3b7jd4gvyg6r6pv7ee1vcd82edzg
366downloads
0stars
1versions
Updated 1mo ago
v0.1.0
MIT-0

Browser Automation with AgentGo Cloud Browsers

AgentGo provides a distributed cloud browser cluster. Connect via WebSocket using chromium.connect() from playwright@1.51.0.

Note: Must use playwright@1.51.0 exactly — newer versions have protocol incompatibilities with AgentGo's server.

Get an API key

Register at https://app.agentgo.live/ — free credits included, no credit card required.

export AGENTGO_API_KEY=your_api_key_here

Install

npm install playwright@1.51.0
# or
pnpm add playwright@1.51.0

Quick start

import { chromium } from "playwright"; // must be playwright@1.51.0

const options = { _apikey: process.env.AGENTGO_API_KEY };
const serverUrl = `wss://app.browsers.live?launch-options=${encodeURIComponent(JSON.stringify(options))}`;

const browser = await chromium.connect(serverUrl);
const page = await browser.newPage();

await page.goto("https://example.com");
const title = await page.title();
console.log(title);

await browser.close();

Connection helper

import { chromium } from "playwright";

export async function connectAgentGo() {
  if (!process.env.AGENTGO_API_KEY)
    throw new Error("AGENTGO_API_KEY is not set");
  const opts = encodeURIComponent(JSON.stringify({ _apikey: process.env.AGENTGO_API_KEY }));
  return chromium.connect(`wss://app.browsers.live?launch-options=${opts}`);
}

Basic interactions

const browser = await connectAgentGo();
const page = await browser.newPage();

await page.goto("https://example.com");
await page.click("button#submit");
await page.fill("input[name=email]", "user@example.com");
await page.press("input[name=email]", "Enter");
await page.screenshot({ path: "screenshot.png" });

await browser.close();

Extract data

const browser = await connectAgentGo();
const page = await browser.newPage();
await page.goto("https://news.ycombinator.com");

const items = await page.$$eval(".titleline a", els =>
  els.map(a => ({ title: a.textContent, href: (a as HTMLAnchorElement).href }))
);

await browser.close();
return items;

Multiple pages (parallel)

const browser = await connectAgentGo();
const [page1, page2] = await Promise.all([browser.newPage(), browser.newPage()]);

await Promise.all([
  page1.goto("https://site-a.com"),
  page2.goto("https://site-b.com"),
]);

await browser.close();

Always close in finally

const browser = await connectAgentGo();
try {
  const page = await browser.newPage();
  await doWork(page);
} finally {
  await browser.close();
}

Specific Tasks

Tips & Anti-Detection

Comments

Loading comments...