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 skills add withoneai/one-agent-plugin --skill browserlessgit clone --depth 1 https://github.com/withoneai/one-agent-pluginWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/withoneai/one-agent-plugin/browserless)<a href="https://agentmods.dev/skills/withoneai/one-agent-plugin/browserless"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/browserless/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/withoneai/one-agent-plugin/browserless"><img src="https://agentmods.dev/badge/skills/withoneai/one-agent-plugin/browserless.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00122 | $0.03369 |
| Opus 5 | $0.00061 | $0.01684 |
| Sonnet 5 | $0.00024 | $0.00674 |
| Haiku 4.5 | $0.00012 | $0.00337 |
Grade A, and why
browserless 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 5d 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.
This is a copy
80% identical to 2-chat — 206 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browserless through One
Browserless is a browser automation platform that provides hosted headless browsers and APIs for Puppeteer, Playwright, and Selenium, allowing developers to run, scale, and manage web scraping, testing, PDF generation, and automation workloads without maintaining browser infrastructure.
One exposes Browserless through four MCP tools. The table below carries real action ids from One's knowledge base, so for a common operation you can skip search and go straight to reading the action's parameters.
How to run an action
- Find the action in the table below, or call
search_one_platform_actionswith platformbrowserlessif it is not listed. - Call
get_one_action_knowledgewith the action id. Do this every time, including for actions in this table. The table gives you the id, not the parameters. - Call
execute_one_actionwith parameters copied from that knowledge.
Never guess a parameter name, a body field, or an enum value. The knowledge has the real schema, and a guessed field is either a 400 or a silent write of the wrong thing.
Before you start
Call list_one_integrations once and confirm Browserless is connected. If it is missing, the user has not connected it: say so and point them at https://app.withone.ai rather than reaching for raw HTTP.
Each connection carries an access field. If it reports {"policy": "methods", "methods": ["GET"]} the agent is read-only here, so plan a read-only answer instead of attempting a write that will be refused.
Before a write
Creates, updates, deletes and sends land on a real Browserless account and cannot be recalled. State the action and the specific target in one line before the first write in a task, and let the user stop you. Reads need no confirmation.
Actions
RenderedHtmlContent
| Action | Method | Path | Action id |
|---|---|---|---|
| Get Rendered HTML Content Using Chromium | POST | /chromium/content |
conn_mod_def::GLXPXuhDvMA::q1YaC644RKm9sGC1F27mmQ |
| Get Rendered HTML Content Using Edge | POST | /edge/content |
conn_mod_def::GLXPbsWIRvA::bAn5eWm6RS2Cnb80EQ9Sew |
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.
- 5d ago First seen · 281 lines · 0 tokens per session scan A bc288c711b5c
browserless is a skill published in the GitHub repository withoneai/one-agent-plugin (1 stars, last pushed 19d ago), licensed MIT. It adds 122 tokens to every session and 3,369 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to 2-chat, differing in 206 lines, and is treated as a copy.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
playwright-cli
A command-line tool for controlling Chromium, Firefox, and WebKit browsers, including navigation, page interaction, screenshots, PDFs, and recorded actions.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…