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/dundas/thinkrun/web-browsenpx skills add dundas/thinkrun --skill web-browsegit clone --depth 1 https://github.com/dundas/thinkrunWrote 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/dundas/thinkrun/web-browse)<a href="https://agentmods.dev/skills/dundas/thinkrun/web-browse"><img src="https://agentmods.dev/badge/skills/dundas/thinkrun/web-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.00096 | $0.01196 |
| Opus 5 | $0.00048 | $0.00598 |
| Sonnet 5 | $0.00019 | $0.00239 |
| Haiku 4.5 | $0.00010 | $0.00120 |
Grade A, and why
web-browse 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 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.
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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Web Browse
Drive a browser programmatically with ThinkRun. Two interfaces, same capabilities:
thinkrunCLI — for shell scripts and terminal use.npm install -g @thinkrun/cli(bin:thinkrun).@thinkrun/mcp— for MCP clients (Claude Code, Cursor, Cline, Windsurf).npx @thinkrun/mcp.
Both support two execution modes:
- Local mode — controls your real Chrome via the ThinkRun extension + native host. Best for sites needing your login/cookies, or visual work on the browser you already have open.
- Cloud mode — provisions an isolated Playwright browser on Fly.io. Best for headless/autonomous scraping, multi-agent work, and anti-detection (stealth).
Mode is auto-detected; override per-command with --mode local|cloud (CLI) or the set_mode tool (MCP).
When to use which
| Scenario | Mode | Why |
|---|---|---|
| Site needs your login cookies | Local | Uses your real Chrome session |
| Visual/interactive work on an open tab | Local | Attach to the tab you're looking at |
| Headless autonomous scraping | Cloud | No Chrome needed, runs detached |
| Multi-agent / parallel sessions | Cloud | Isolated browser per session |
| Anti-detection needed | Cloud | Built-in stealth (no navigator.webdriver) |
See references/details.md for the full CLI command + MCP tool reference, common patterns, and error codes.
Setup
Install
# CLI (shell use)
npm install -g @thinkrun/cli # provides the `thinkrun` command
# MCP (Claude Code / Cursor / Cline / Windsurf)
npx @thinkrun/mcp # or add to your MCP config (see below)
MCP config:
{ "mcpServers": { "thinkrun": { "command": "npx", "args": ["@thinkrun/mcp"] } } }
Cloud mode
Set an API key (get one at thinkrun.ai):
thinkrun config set-key <api-key> # or: export THINKRUN_API_KEY=<api-key>
What ships with it
2 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 · 125 lines · 96 tokens per session scan A 4802e1b0d050
web-browse is a skill published in the GitHub repository dundas/thinkrun (1 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,196 once invoked, about $0.0005 per session on Opus 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-31.
Other skills, from other repositories
Agent Browser Automation
Fast Rust-based headless browser automation CLI with Node.js fallback for AI agents, featuring navigation, clicking, typing, snapshots, and structured commands optimized for agent workflows.
real-browser-control
Connect an AI coding agent to the user's REAL Chrome via Real Browser MCP (local MCP server + Chrome extension over localhost WebSocket). Use for live UI verification, already-open tabs, existing cookies/SSO/2FA, staging admin panels, and any task where headless Playwright or a cloud agentic browser would miss the…
browser-automation
Control the user's real logged-in Chrome via Real Browser MCP (extension + local MCP). Use for live UI checks, existing SSO/cookies, and tabs already open. Triggers: real browser, my Chrome, not headless, verify in browser. Prefer over Playwright when session state matters. Prefer Playwright for CI.
Browser-Use Automation
CLI tool for persistent browser automation with multi-session support, featuring Chromium/Real/Remote browser modes, cookie management, JavaScript execution, and long-running automation workflows.
aipex-browser
AI-powered browser automation using the AIPex Chrome Extension via MCP bridge. Use this skill when the agent needs to control a Chrome browser — navigating pages, clicking elements, filling forms, capturing screenshots, managing tabs, or downloading content — by connecting to the AIPex MCP bridge.
playwright-api
API testing skill using Playwright's built-in APIRequestContext for RESTful service validation, authentication flows, and API contract verification.