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/agentproto/ts/local-browsernpx skills add agentproto/ts --skill local-browsergit clone --depth 1 https://github.com/agentproto/tsWhat 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.00054 | $0.01103 |
| Opus 5 | $0.00027 | $0.00551 |
| Sonnet 5 | $0.00011 | $0.00221 |
| Haiku 4.5 | $0.00005 | $0.00110 |
Grade A, and why
local-browser 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Reach for this skill whenever the task needs to act AS THE USER in a web context. The hallmark is: an unauthenticated browser can't do this because the page requires their cookies/session.
- "Post this to LinkedIn / Twitter / Reddit" — needs their logged-in session.
- "Check my Gmail / Slack / Linear for X" — same.
- "Pull this from behind SSO."
- "Place this order on Amazon / book this flight" — payment + saved cards + addresses.
- "Comment on this PR / file this Jira ticket" — authored as them.
If the page is public and unauthenticated, prefer a regular fetch / plain scraping tool — driving a real browser is overkill and the cookies are sensitive.
What it is
The local-browser plugin (@agentproto/plugin-local-browser) is a
one-time setup that:
- Clones one of the user's existing Chrome profiles into
~/.agentproto/chrome-profile/(cookies + extensions + logins transfer). - Installs
chrome-devtools-mcpinto~/.agentproto/chrome-mcp/. - Registers it in
~/.agentproto/imported-mcps.jsonso the agentproto daemon proxies all 29 browser tools through/mcpto every tunnel-connected client.
The daemon spawns Chrome on demand against the cloned profile, so the user's daily Chrome keeps running undisturbed.
How to call it
Tools surface under the alias local-browser. From an agentproto
MCP-proxy client they're invoked via the daemon's meta-tools:
// list everything available
mcp_imported_tool_list({ alias: "local-browser" })
// drive the browser
mcp_imported_call({
alias: "local-browser",
tool: "navigate_page",
arguments: { url: "https://news.ycombinator.com" }
})
The 29 tools fall into these buckets:
| What you want | Tool(s) |
|---|---|
| Open / switch pages | new_page, navigate_page, select_page, list_pages, close_page |
| See the page | take_snapshot (AX tree), take_screenshot, list_console_messages |
| Click / type / fill | click, type_text, fill, fill_form, press_key, hover, drag |
| Wait for something | wait_for |
| Run JS | evaluate_script |
| Network inspection | list_network_requests, get_network_request |
| Perf / Lighthouse | performance_start_trace, performance_stop_trace, lighthouse_audit |
| Files / dialogs / viewport | upload_file, handle_dialog, resize_page, emulate |
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 · 116 lines · 54 tokens per session scan A f3aa9fc2368b
local-browser is a skill published in the GitHub repository agentproto/ts (5 stars, last pushed 2d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,103 once invoked, about $0.0003 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-31.
Other skills, from other repositories
directory-management
Manages project directory setup and artifact organization. Use when starting a new project, resuming an existing one, or when a PLAN.md needs to be associated with a project directory. Creates the project folder structure (specs/, scripts/, notebooks/, manifests/, agentmemory/) and resolves project naming.
backlog
Capture single backlog items, or list and triage an existing project backlog. Use this skill whenever the user wants to file a bug, feature request, or backlog item without writing a full PRD, including casual requests mid-conversation like "create an issue for that", "add this to the backlog", or "file a quick bug…
transformers-js
Build and validate local browser or Bun inference with Hugging Face Transformers.js, WebGPU or WASM backends, quantization, caching, and cleanup.
process-hygiene
Clean up orphaned browser/test/dev-server processes safely after test bursts.
browser-qa
Validate web applications through the embedded browser with responsive, interaction, console, and screenshot checks.
scene-designer
Activate this skill when users need help creating, modifying, or arranging visual elements in OBS scenes. Triggers include requests like "add a text overlay", "create a new scene", "move my webcam", "resize the game capture", "add a browser source", "arrange my layout", or designing scene compositions. This skill…