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 commands/compnew2006/browser-controller/check-browsergit clone --depth 1 https://github.com/compnew2006/browser-controllerWhat 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.00000 | $0.00384 |
| Opus 5 | $0.00000 | $0.00192 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
check-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 yesterday.
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.
What it actually says
check-browser
Use Browser Controller to check what's currently showing in my browser.
Steps
- Call
browser_tabs { action: "list" }to get atabId - Call
browser_snapshot { tabId }to see the current page structure (refs are tab-scoped) - Based on what you find, take a
browser_screenshot { tabId }if visual verification is needed - Report back what you see - page title, key elements, any errors or unexpected state
- If I asked you to verify something specific, focus on that
When to use
- After making a code change, to verify it rendered correctly
- To check if a form works, a button does what it should, or content loaded
- To read page content I'm looking at
- To debug visual issues or check responsive layout
Reading the snapshot efficiently
isNew: trueon a ref means that element appeared since the last snapshot — focus on those when something just changed (e.g. an overlay opened after a click). You don't need to re-read the whole tree.- After
browser_scroll, expectrefsMayBeStale: true— re-snapshot before interacting on feeds like Facebook/Instagram that recycle DOM nodes. - If a click returns
freshRefs, the element was scrolled away — retry with one of the new refs in the same response (no separate snapshot needed).
Important
- This is my REAL browser. I'm already logged in everywhere.
- Always pass
tabId— never assume the active tab is the one to act on. - Don't close tabs I didn't ask you to close.
- Don't navigate away from the current page unless I ask you to.
- Use element refs from snapshots for any interactions; refs are valid only for the tabId that produced them.
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.
- yesterday First seen · 33 lines · 0 tokens per session scan A 938f779fa770
check-browser is a command published in the GitHub repository compnew2006/browser-controller (1 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 384 tokens. 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 commands, from other repositories
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
auto-browse
Auto-browse — learn, optimize, and graduate browser operations or web data-mining workflows.
research-perplexity
Run a deep research query using Perplexity's /research mode via Playwright browser automation. This is an alternative to /export-to-council that uses Perplexity's dedicated research mode instead of multi-model council.
review
Compare a reference design against an implementation. Accepts Figma URL, image file, or browser URL as reference.
graphify
Turn your vault into a clustered knowledge graph with HTML and JSON outputs.
laravel-playwright
E2E Playwright patterns; use the laravel:e2e-playwright skill exactly as written.