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.
git clone --depth 1 https://github.com/heymegabyte/claude-skillsWrote 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/agents/heymegabyte/claude-skills/browser-operator)<a href="https://agentmods.dev/agents/heymegabyte/claude-skills/browser-operator"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/browser-operator/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/agents/heymegabyte/claude-skills/browser-operator"><img src="https://agentmods.dev/badge/agents/heymegabyte/claude-skills/browser-operator.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.00086 | $0.00743 |
| Opus 5.5 | $0.00034 | $0.00297 |
| Sonnet 5.5 | $0.00017 | $0.00149 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
browser-operator 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 13d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 13d ago First seen · 51 lines · 86 tokens per session scan A 9d893fdc2eb3
browser-operator is an agent published in the GitHub repository heymegabyte/claude-skills (22 stars, last pushed 12d ago), with no licence file. It adds 86 tokens to every session and 743 once invoked, about $0.0003 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-10-03.
Other agents, from other repositories
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
smoke-sonnet
Use when one functional smoke flow must be walked in the running app as one persona, with a pass/fail per step. Needs the chrome-devtools MCP server. Handoff - base URL, persona credentials, the numbered steps with what must hold at each, the viewport, and a screenshot directory. Returns a step table; visual doubts…
browser-qa-agent
QA engineer with Chrome integration. Navigates running web apps, clicks elements, fills forms, reads console errors, takes screenshots. Use for interactive UI testing on localhost or deployed apps.
feature-verifier
Drives a feature's golden path + one error path through the LIVE app using the Playwright CLI (a throwaway Node script run headless), screenshots each step, and writes a verification doc to .brain/features/ /verifications/ .md. Replaces writing per-feature e2e specs. Use for any user-visible feature/flow before…
ui-ux-tester
Use this agent when you need exhaustive UI and UX functionality testing driven by documented user flows, with browser or desktop interaction tooling and structured defect reporting.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.