Agent Browser
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
Write PandaScript agent scripts (.js) — Lightpanda's replayable browser-automation format, run token-free with lightpanda agent script.js.
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lightpanda-io/agent-skill pandascript --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pandascript .claude/skills/pandascript && rm -rf skills-srcUse ~/.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/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .claude/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lightpanda-io/agent-skill/tree/main/pandascriptType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lightpanda-io/agent-skill pandascript --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pandascript .agents/skills/pandascript && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .agents/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lightpanda-io/agent-skill pandascript --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pandascript .cursor/skills/pandascript && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .cursor/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lightpanda-io/agent-skill.git --path pandascript--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lightpanda-io/agent-skill pandascript --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pandascript .gemini/skills/pandascript && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .gemini/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lightpanda-io/agent-skill pandascriptInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .github/skills && cp -r skills-src/pandascript .github/skills/pandascript && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .github/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lightpanda-io/agent-skill --skill pandascript -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lightpanda-io/agent-skill pandascript --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lightpanda-io/agent-skill.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pandascript .opencode/skills/pandascript && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "pandascript" agent skill from https://github.com/lightpanda-io/agent-skill/tree/main/pandascript into .opencode/skills/pandascript/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "pandascript", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
pandascriptWrite PandaScript agent scripts (.js) — Lightpanda's replayable browser-automation format, run token-free with lightpanda agent script.js.
Pandascript is an agent skill from lightpanda-io/agent-skill. Write PandaScript agent scripts (.js) — Lightpanda's replayable browser-automation format, run token-free with lightpanda agent script.js.
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Productivity & Automation, covering Browser automation. The repository describes itself as: Lightpanda browser skill for openclaw. The licence is Apache-2.0.
9 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 387702e. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
news.ycombinator.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
LP_HN_PASSWORDFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Pandascript loads about 2.7k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 1,196 words of instructions outside code blocks.
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.
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); files beside SKILL.md are not scanned.
The full file from lightpanda-io/agent-skill at commit 387702e, republished under its Apache-2.0 licence (© lightpanda-io). 1,196 words, ~2,703 tokens.
.claude/skills/pandascript/SKILL.md (or your agent's skills folder).Run with:
./lightpanda agent script.jsThe script runs in its own V8 context — neither the page nor Node.js:
Page is the only global. new Page() makes a page and await page.goto(url) navigates it; every other primitive is a method on that page: const page = new Page(); await page.goto(url); page.extract({...}); page.click(sel);.window, document, DOM, localStorage — read pages with page.extract(...), run page-side JS only via page.evaluate("...").require, process, fs, npm. Standard ECMAScript built-ins only (JSON, Map, template literals, …).page.goto(...) is async — always await it. Page methods are synchronous: const data = page.extract({...}), never await page.extract(...). The script body runs as an async function, so top-level await is allowed.await page.goto(url2) keeps page valid and points it at the new URL, discarding the old page — read it before navigating away. Independent URLs don't share a page: make a new Page() for each and load them in parallel (fan-out, best practice 2).evaluate("...") cannot see script variables — interpolate values into the string. Script code cannot see page variables.return <value> is the script's output, printed automatically (objects/arrays as JSON). End with return page.extract({...}); or return results;. A bare trailing expression is NOT printed; neither is console.log(JSON.stringify(...)).Page is the only global; new Page() makes a page and everything else is a method on it.
| Call | Notes |
|---|---|
new Page() | Makes a page object. No navigation yet — call page.goto(url) before any other method. Make several to navigate in parallel (fan-out, best practice 2). |
page.close() | Marks the page done; later method calls on it error. The page is otherwise reclaimed at script end. |
await page.goto(url[, { timeout }]) | Async — must be awaited. Navigates the page (re-navigating reuses the same object). Waits for load. Rejects on navigation failure; a timeout does NOT reject (the page may still be usable). Default timeout 10000 ms. |
page.evaluate(script[, { url, timeout, save }]) | Page-side JS escape hatch; returns text (JSON for objects/arrays). |
page.extract(schema) | The only primitive returning a real JS value (object/array). The schema is its only argument. See schema below. |
page.click(selector) | |
page.fill(selector, value) | |
page.scroll([{ x, y }]) | |
page.waitForSelector(selector[, { timeout }]) | waitFor* default timeout 5000 ms. |
page.waitForScript(script[, { timeout }]) | Re-evaluates page JS until truthy. |
page.waitForState(state[, { timeout }]) | state: one of "load", "domcontentloaded", "networkalmostidle", "networkidle", "done". |
page.hover(selector) | |
page.press(selector, key) | Selector first! page.press("Enter") binds "Enter" to selector and fails — use page.press(null, "Enter") or page.press({ key: "Enter" }). |
page.selectOption(selector, value) | |
page.setChecked(selector[, checked]) | checked defaults to true. |
Options (the trailing { … } object; every option may be omitted):
goto: timeout — Optional timeout in milliseconds. Defaults to 10000.evaluate: url — Optional URL to navigate to before evaluating. timeout — Optional timeout in milliseconds. Defaults to 10000. save — Optional bridge-store key. The evaluate's return value is stored under this name and re-exposed as lp.<name> to subsequent evaluates. Objects, arrays, and strings are serialized automatically — no JSON.stringify needed.scroll: x — Optional: The horizontal scroll offset. y — Optional: The vertical scroll offset.waitForSelector: timeout — Optional timeout in milliseconds. Defaults to 5000.waitForScript: timeout — Optional timeout in milliseconds. Defaults to 5000.waitForState: timeout — Optional timeout in milliseconds. Defaults to 5000.Calling convention: leading positionals + optional trailing options object, or one object with everything (page.waitForSelector("#row", { timeout: 2000 }) ≡ page.waitForSelector({ selector: "#row", timeout: 2000 })). A bare option positional (page.waitForSelector("#row", 2000)) and a field passed both ways are invalid arguments. null skips a positional. Arguments must be JSON-serializable.
CSS selectors only — backendNodeIds don't exist here. Standard CSS only: no jQuery :contains() or Playwright :has-text().
Keys = output field names; values pick what to lift (not a JSON Schema):
const { stories } = page.extract({
stories: [{
selector: "tr.athing", // one record per match
limit: 5,
fields: { // resolved relative to each match
title: ".titleline > a", // first match's text (null if missing)
url: { selector: ".titleline > a", attr: "href" },
text: "" // "" = the matched element's own text
}
}]
});"sel" → first match's text; ["sel"] → all matches' text; { selector, attr } / [{ selector, attr }] → attribute(s); limit: N caps any array form.save: option in scripts — keep results in variables.await page.goto on a dynamic page (feeds, search results, comment threads), call page.waitForState("networkidle") or page.waitForSelector(...) before extracting. Most static pages are complete at load — don't wait blindly.const list = new Page();
await list.goto(listUrl);
const { items } = list.extract({ items: [{ selector: "a.row", fields: { url: { attr: "href" } } }] });
const pages = items.map(() => new Page());
await Promise.all(pages.map((p, i) => p.goto(items[i].url))); // all in flight at once
return pages.map((p, i) => ({ ...items[i], ...p.extract({ /* schema */ }) }));--http-max-concurrent) and 6 per host (--http-max-host-open, the browser default — raising it much higher risks overwhelming the target server). Extra navigations queue rather than fail, so a same-site fan-out loads ~6 pages at a time. For long lists, fan out in batches and page.close() each page once read so its memory is reclaimed.Promise.all rejects the whole batch if any goto fails (a timeout does not reject); use Promise.allSettled when partial results are fine.for (const it of items) { await page.goto(it.url); … }) only when the steps depend on each other — each page decides the next URL, or they share login/session state.evaluate is a last resort, not a reading tool. A querySelectorAll-and-parse page.evaluate block is always wrong: lift the raw strings with page.extract, then trim/split/parse them in top-level JS. Reserve page.evaluate for behavior that must run inside the page and no builtin covers — and remember its state dies on every navigation/reload, while script variables persist.$LP_* placeholders in any string argument (page.fill("#pw", "$LP_HN_PASSWORD")). Never inline a real secret; placeholders resolve inside the Lightpanda process.input[type="submit"][value="login"], not input[type="submit"].try/catch where you have a real fallback (e.g. optional cookie banner: try { page.click("#accept") } catch {}).return <result>. console.log is for debug output only and doesn't JSON-format objects.const/let, for (const x of xs), template literals, destructuring, 2-space indent.// comment above each logical step describing what it accomplishes toward the goal (not restating the call). One comment per block, not per line — skip self-evident lines:// Load the Hacker News front page
const page = new Page();
await page.goto("https://news.ycombinator.com");
// Pull the top 5 stories (title + link)
const { stories } = page.extract({ stories: [{ selector: "tr.athing", limit: 5, fields: { title: ".titleline > a", url: { selector: ".titleline > a", attr: "href" } } }] });
// Open each story page in parallel and read its text
const pages = stories.map(() => new Page());
await Promise.all(pages.map((p, i) => p.goto(stories[i].url)));| Error | Cause / fix |
|---|---|
extract is not defined (or click/fill/…) | These are methods on the page object, not globals → const page = new Page(); await page.goto(url); page.extract(...) |
Page must be called with new | Page(...) called without new → const page = new Page(); |
page is not navigated or has been closed | A method on a fresh new Page() (or a closed page) → await page.goto(url) first |
page handle is no longer valid | Used a page after a later goto on the same page replaced it → read it before navigating away. Sibling pages from other new Page() calls stay valid. |
document is not defined | DOM API in script context → use page.extract or page.evaluate |
require is not defined | Not Node.js |
no page loaded - run page.goto(url) first | Page method before navigation |
invalid arguments | Wrong arity/shape, non-JSON value, or a field set both positionally and in options |
extract: no schema selector matched any element | All schema fields missed → fix selectors |
press fails with one string arg | Selector-first: use page.press(null, "Enter") or page.press({ key: "Enter" }) |
© lightpanda-io, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in pandascript of lightpanda-io/agent-skill.
Open the folder on GitHubat commit 387702e
Pandascript 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Pandascript this skilllightpanda-io/agent-skill | 101 | — | ~2.7k | Automated safety check: Pass | Apache-2.0 | |
| Agent Browserquran/quran.com-frontend-next | 1.9k | 42 repos | ~3.3k | Automated safety check: Pass | None | |
| Dev-Browser CLI AutomationSawyerHood/dev-browser | 6.7k | 1 repos | ~455 | Automated safety check: Pass | MIT | |
| Agent Browsersuperagent-ai/grok-cli | 3.5k | 1 repos | ~633 | Automated safety check: Pass | MIT | |
| Browser Automationopenclaw/openclaw | 392k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Camoufox CLIBin-Huang/camoufox-cli | 350 | 1 repos | ~4.5k | Automated safety check: Pass | MIT |
quran/quran.com-frontend-next
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
SawyerHood/dev-browser
Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web…
superagent-ai/grok-cli
Use the host-side agent-browser CLI for local browser smoke tests, screenshots, snapshots, and simple UI validation against forwarded localhost URLs.
openclaw/openclaw
A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.
Bin-Huang/camoufox-cli
Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.
VibiumDev/vibium
Automate browsers with the Vibium CLI. An agent skill from VibiumDev/vibium.
lightpanda-io/agent-skill
Lightpanda browser, drop-in replacement for Chrome-based browsing in any AI agent - faster and lighter for tasks without graphical rendering like data retrieval.
Categories
Write PandaScript agent scripts (.js) — Lightpanda's replayable browser-automation format, run token-free with lightpanda agent script.js. Pandascript is an agent skill from lightpanda-io/agent-skill.js.
Pandascript fits situations like: tasks that involve Browser automation.
Run `npx skills add lightpanda-io/agent-skill --skill pandascript -a claude-code`. Or copy the skill folder (pandascript in lightpanda-io/agent-skill) into .claude/skills/pandascript in your project. Claude Code loads it when a task matches its description.
Run `npx skills add lightpanda-io/agent-skill --skill pandascript -a codex`. Or copy the skill folder (pandascript in lightpanda-io/agent-skill) into .agents/skills/pandascript in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lightpanda-io/agent-skill --skill pandascript -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/pandascript, .gemini/skills/pandascript, .github/skills/pandascript and .opencode/skills/pandascript in your project.
Going by SKILL.md and its folder, Pandascript needs credentials named LP_HN_PASSWORD. Our summary lists: Node.js.
SKILL.md names 1 domain. In commands or code: news.ycombinator.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
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. Review the folder before installing.
Pandascript is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Pandascript: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dev-Browser CLI Automation (SawyerHood/dev-browser, 6.7k stars), Agent Browser (superagent-ai/grok-cli, 3.5k stars) and Browser Automation (openclaw/openclaw, 392k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
lightpanda-io (a GitHub organization) maintains it in lightpanda-io/agent-skill, which has 101 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: lightpanda-io/agent-skill on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.