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/yc-software/qm/browsenpx skills add yc-software/qm --skill browsegit clone --depth 1 https://github.com/yc-software/qmWrote 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/yc-software/qm/browse)<a href="https://agentmods.dev/skills/yc-software/qm/browse"><img src="https://agentmods.dev/badge/skills/yc-software/qm/browse.svg" alt="Measured on agentmods" 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 | $0.00101 | $0.04544 |
| Opus 5 | $0.00051 | $0.02272 |
| Sonnet 5 | $0.00020 | $0.00909 |
| Haiku 4.5 | $0.00010 | $0.00454 |
Grade A, and why
browse scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Drive a real stealth browser from your shell — act on websites (order food, file an expense, pull data behind a login), with per-person persistent sign-ins via the provider's managed auth (Kernel, Anchor, or How it starts
The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browse (the skill-based browser)
This is the platform's browser: the logic lives in this skill and runs in your shell; only
the heavy runtime (browser-use + Chromium) is baked into your computer's image at
/opt/browser-engine/venv. The browser itself is a remote stealth browser you drive over
CDP, hosted by whichever provider the deployment configures. It is slow and expensive — for acting on a site, not
reading one. To retrieve information (read a page, check a price, hit an API), reach for
curl/wget first; browse only when you must interact — sign in, fill and submit forms,
click through a flow — or when a plain fetch is genuinely blocked by heavy JS or a bot wall.
(To verify a localhost site you built, don't use this at all — a remote browser can't reach
your loopback; use the local headless chromium binary.)
Pick the provider
Which provider you use is decided by which API key is available in your env (or obtainable through the keychain). Org keys arrive automatically: an admin saves a provider's key as an org credential delivered as sandbox env (admin UI → Service credentials → delivery "Sandbox env"), and it rides into every all-internal conversation — nothing here is deploy config. A person's own keychain key overrides the org one. Keys you may see today:
KERNEL_API_KEY→ Kernel (onkernel.com). Readskills/browse/providers/kernel.md.ANCHOR_API_KEY→ Anchor (anchorbrowser.io). Readskills/browse/providers/anchor.md.BROWSERBASE_API_KEY→ Browserbase (browserbase.com). Readskills/browse/providers/browserbase.md.- Another
*_API_KEYalongside askills/browse/providers/<name>.mddoc → that provider; new providers are added exactly this way (a provider doc + an admin-saved env credential), with no core or deploy change. - Several set → the first in the order above, unless the person asks for another or the chosen key is rejected (401/403 on browser create) — a dead key means that provider is absent, not that browsing is.
- None set → org-key browsing is off here (externals in the room, or the admin saved no provider key). Say so rather than hunting for keys.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 334 lines · 101 tokens per session scan A 63f36fd119bf
browse is a skill published in the GitHub repository yc-software/qm (14,533 stars, last pushed today), licensed MIT. It adds 101 tokens to every session and 4,544 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
firecrawl
Search the web and scrape pages into clean markdown with the Firecrawl API — query-based discovery, single-URL extraction including public PDFs, driven by curl with a vault-stored API key.
penguin-harness-manual-test
Use when standing PenguinHarness up to try a change by hand — launching the Web App, the desktop shell, the landing page or the docs site to click through it, screenshot it, or reproduce a report. Covers the four dev entry points and their ports, which data root each writes to, and the four ways a healthy setup looks…
host-computer-use
Beta desktop control through the connected A0 CLI host. Use for the user's host/local computer screenshots, screen inspection, menus, native app UI, OS-level clicking, scrolling, typing, or checking computeruseremote status. Use instead of linux-desktop for host/local machine control. Do not use for ordinary browser…
browser-automation
Use for complex Agent Zero browser automation, including multi-tab browsing, screenshots, forms, uploads, raw pointer/keyboard actions, host-vs-container browser mode, and visual verification workflows.
browser-extension-control
Create, inspect, install, and safely maintain Chrome extensions for Agent Zero's built-in Browser plugin. Use when the user asks to build a browser extension, modify an existing extension, install a Chrome Web Store extension, or review extension permissions.
browser-form-workflows
Use for complex Agent Zero Browser form workflows involving selects, checkboxes, radios, file uploads, contenteditable fields, multi-step validation, or visually verified submission.