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/ottermind/youclaw/agent-browsernpx skills add OtterMind/youclaw --skill agent-browsergit clone --depth 1 https://github.com/OtterMind/youclawWhat 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.00042 | $0.01746 |
| Opus 5 | $0.00021 | $0.00873 |
| Sonnet 5 | $0.00008 | $0.00349 |
| Haiku 4.5 | $0.00004 | $0.00175 |
Grade A, and why
agent-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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with agent-browser
Performance Rules (CRITICAL)
- ALWAYS chain commands with
&&when you don't need intermediate output. Each separate tool call costs seconds of round-trip latency. - ALWAYS combine open + wait + snapshot into one call:
agent-browser open <url> && agent-browser wait --load load && agent-browser snapshot -i - ALWAYS batch multiple interactions (fill, click, select) into one
&&chain when refs are already known. - Use
--load load(DOM load event) by default. Only usenetworkidlewhen you specifically need all XHR/fetch to complete (e.g., waiting for API-driven content). - Do NOT snapshot after every interaction — only re-snapshot when you need to discover new element refs (after navigation or major DOM changes).
Core Workflow
Every browser automation follows this pattern:
- Navigate + Snapshot (one call):
agent-browser open <url> && agent-browser wait --load load && agent-browser snapshot -i - Interact: Batch all interactions using known refs in one
&&chain - Re-snapshot: Only after navigation or major DOM changes
# Step 1: Open and discover elements (ONE tool call)
agent-browser open https://example.com/form && agent-browser wait --load load && agent-browser snapshot -i
# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit"
# Step 2: Batch all interactions (ONE tool call)
agent-browser fill @e1 "[email protected]" && agent-browser fill @e2 "password123" && agent-browser click @e3 && agent-browser wait --load load
# Step 3: Only snapshot if you need to verify or discover new elements
agent-browser snapshot -i
This reduces 7+ round-trips to just 2-3.
Essential Commands
# Navigation
agent-browser open <url> # Navigate (aliases: goto, navigate)
agent-browser close # Close browser
# Snapshot
agent-browser snapshot -i # Interactive elements with refs (recommended)
agent-browser snapshot -i -C # Include cursor-interactive elements
agent-browser snapshot -s "#selector" # Scope to CSS selector
# Interaction (use @refs from snapshot)
agent-browser click @e1 # Click element
agent-browser fill @e2 "text" # Clear and type text
agent-browser type @e2 "text" # Type without clearing
agent-browser select @e1 "option" # Select dropdown option
agent-browser check @e1 # Check checkbox
agent-browser press Enter # Press key
agent-browser scroll down 500 # Scroll page
# Get information
agent-browser get text @e1 # Get element text
agent-browser get url # Get current URL
agent-browser get title # Get page title
# Wait
agent-browser wait @e1 # Wait for element
agent-browser wait --load load # Wait for DOM load (fast, preferred)
agent-browser wait --load networkidle # Wait for network idle (slow, use only when needed)
agent-browser wait --url "**/page" # Wait for URL pattern
agent-browser wait 2000 # Wait milliseconds
# Capture
agent-browser screenshot # Screenshot to temp dir
agent-browser screenshot --full # Full page screenshot
agent-browser screenshot --annotate # Annotated screenshot with numbered element labels
agent-browser pdf output.pdf # Save as PDF
# Diff (compare page states)
agent-browser diff snapshot # Compare current vs last snapshot
agent-browser diff screenshot --baseline before.png # Visual pixel diff
agent-browser diff url <url1> <url2> # Compare two pages
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.
- 3d ago First seen · 194 lines · 42 tokens per session scan A 3d7f39993297
agent-browser is a skill published in the GitHub repository OtterMind/youclaw (724 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 1,746 once invoked, about $0.0002 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-30.
Other skills, from other repositories
add-tavily-tool
Add Tavily Search and Extract as keyless remote MCP tools for selected NanoClaw agent groups. Use when installing Tavily web search or URL extraction without an API key.
agent-browser
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
browser-cdp
Use this skill when you need to control a Chrome browser via CDP (Chrome DevTools Protocol) to reuse existing login sessions. Covers: launching Chrome in debug mode, opening URLs, waiting for page load, evaluating JavaScript, taking snapshots, and extracting auth tokens. Trigger phrases: browser automation, CDP…
anysearch
Real-time search engine supporting web search, vertical domain search, parallel batch search, and URL content extraction.
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.
browser-automation
Playwright-based browser automation patterns for autonomous web interaction.