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 patleeman/neon-pilot --skill browsergit clone --depth 1 https://github.com/patleeman/neon-pilotWrote 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/patleeman/neon-pilot/browser)<a href="https://agentmods.dev/skills/patleeman/neon-pilot/browser"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/browser/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/patleeman/neon-pilot/browser"><img src="https://agentmods.dev/badge/skills/patleeman/neon-pilot/browser.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.00034 | $0.02356 |
| Opus 5.5 | $0.00014 | $0.00942 |
| Sonnet 5.5 | $0.00007 | $0.00471 |
| Haiku 4.5 | $0.00003 | $0.00236 |
Grade A, and why
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 2mo 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Built-in Workbench Browser
The built-in Browser is the user-facing browser surface inside the Electron desktop app's Workbench layout.
Use this extension skill when work touches:
- the right-side Workbench Browser tab
- browser comments attached to composer prompts
- browser snapshot/action behavior inside Electron
- the boundary between the built-in browser and the
agent-browserCLI/dev tool
Product model
The Workbench Browser is an Electron-owned WebContentsView embedded in the desktop app.
It is for:
- letting the user browse a page beside a conversation
- letting the user right-click page elements and attach comments to the next prompt
- giving agents and the user a shared, visible page context for communication
It is not a general-purpose replacement for Chrome, and it should not expose agent/debug controls directly to normal users.
This distinction matters in prompts: the built-in browser tools are a communication tool. Use them when the user is showing the agent a page, asking about the visible Workbench Browser, or wants the agent to act on the same page they can see. Do not treat them as the default development automation harness.
User-facing behavior
The Browser tab should stay boring:
- Back and forward controls
- Reload/stop icon control
- URL field; pressing Enter navigates
- page viewport
- right-click menu item: Comment on this
Do not show agent-only controls such as JSON action batches, raw snapshots, or automation debug output in the user UI. If those capabilities exist, keep them behind agent/tool APIs or developer diagnostics.
Browser comments
Right-clicking inside the browser and choosing Comment on this captures a target bundle and opens a small comment box over the page.
The target bundle should include enough metadata for both humans and agents:
- URL and page title
- best-effort selector
- XPath/DOM fallback
- role and accessible name
- test id when present
- element text and nearby text
- trimmed HTML preview
- viewport rect, scroll position, and device pixel ratio
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.
- 2mo ago First seen · 251 lines · 34 tokens per session scan A 77d7cc042651
browser is a skill published in the GitHub repository patleeman/neon-pilot (23 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 2,356 once invoked, about $0.0001 per session on Opus 5.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.
browser compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| browserpatleeman/neon-pilot | Skill | 23 | 3mo ago | MIT | A | 34 | Claude Code, Codex |
| interactive-loginyc-software/qm | Skill | 16k | yesterday | MIT | A | 46 | Claude Code, Codex |
| pinchtab-mcppinchtab/pinchtab | Skill | 11k | 10d ago | MIT | A | 52 | Claude Code, Codex |
| azure-messaging-webpubsub-javamicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 43 | Claude Code |
| cua-driverdavidondrej/skills | Skill | 4.3k | 3d ago | MIT | A | 68 | Claude Code, Codex |
| open-design-browsercompozy/compozy | Skill | 2.8k | yesterday | MIT | A | 56 | Claude Code, Codex |
| southwestborski/travel-hacking-toolkit | Skill | 895 | yesterday | MIT | A | 40 | Claude Code |