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 agentmods add skills/lightpanda-io/agent-skill/pandascriptnpx skills add lightpanda-io/agent-skill --skill pandascriptgit clone --depth 1 https://github.com/lightpanda-io/agent-skillWhat 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 | $0.00036 | $0.02725 |
| Opus 5 | $0.00018 | $0.01362 |
| Sonnet 5 | $0.00007 | $0.00545 |
| Haiku 4.5 | $0.00004 | $0.00272 |
Grade A, and why
pandascript 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 2d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Lightpanda agent scripts
Run with:
./lightpanda agent script.js
Mental model (get this right first)
The script runs in its own V8 context — neither the page nor Node.js:
Pageis the only global.new Page()makes a page andawait 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);.- No
window,document, DOM,localStorage— read pages withpage.extract(...), run page-side JS only viapage.evaluate("..."). - No
require,process,fs, npm. Standard ECMAScript built-ins only (JSON,Map, template literals, …). page.goto(...)is async — alwaysawaitit. Page methods are synchronous:const data = page.extract({...}), neverawait page.extract(...). The script body runs as an async function, so top-levelawaitis allowed.- Re-navigating reuses the same page:
await page.goto(url2)keepspagevalid and points it at the new URL, discarding the old page — read it before navigating away. Independent URLs don't share a page: make anew Page()for each and load them in parallel (fan-out, best practice 2). - Page
evaluate("...")cannot see script variables — interpolate values into the string. Script code cannot see page variables. - Variables persist across navigations within one run, so cross-page aggregation is plain JS.
return <value>is the script's output, printed automatically (objects/arrays as JSON). End withreturn page.extract({...});orreturn results;. A bare trailing expression is NOT printed; neither isconsole.log(JSON.stringify(...)).
Primitives
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. |
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.
- 2d ago First seen · 136 lines · 36 tokens per session scan A e163426d7026
pandascript is a skill published in the GitHub repository lightpanda-io/agent-skill (95 stars, last pushed 5d ago), licensed Apache-2.0. It adds 36 tokens to every session and 2,725 once invoked, about $0.0002 per session on Opus 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-30.
Other skills, from other repositories
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
playwright
Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.