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/sumulige/sumulige-claude/agent-browsernpx skills add sumulige/sumulige-claude --skill agent-browsergit clone --depth 1 https://github.com/sumulige/sumulige-claudeWrote 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/sumulige/sumulige-claude/agent-browser)<a href="https://agentmods.dev/skills/sumulige/sumulige-claude/agent-browser"><img src="https://agentmods.dev/badge/skills/sumulige/sumulige-claude/agent-browser.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.1 | $0.00108 | $0.01721 |
| Opus 5 | $0.00054 | $0.00860 |
| Sonnet 5 | $0.00022 | $0.00344 |
| Haiku 4.5 | $0.00011 | $0.00172 |
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 5d 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.
This is a copy
100% identical to agent-browser — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with agent-browser
Core Workflow
Every browser automation follows this pattern:
- Navigate:
agent-browser open <url> - Snapshot:
agent-browser snapshot -i(get element refs like@e1,@e2) - Interact: Use refs to click, fill, select
- Re-snapshot: After navigation or DOM changes, get fresh refs
agent-browser open https://example.com/form
agent-browser snapshot -i
# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit"
agent-browser fill @e1 "[email protected]"
agent-browser fill @e2 "password123"
agent-browser click @e3
agent-browser wait --load networkidle
agent-browser snapshot -i # Check result
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 (divs with onclick, cursor:pointer)
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 networkidle # Wait for network idle
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 pdf output.pdf # Save as PDF
What ships with it
9 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.
- references/authentication.md 4.9 KB
- references/commands.md 9.3 KB
- references/proxy-support.md 4.6 KB
- references/session-management.md 4.2 KB
- references/snapshot-refs.md 4.2 KB
- references/video-recording.md 3.5 KB
- templates/authenticated-session.sh 3.2 KB runs code
- templates/capture-workflow.sh 1.8 KB runs code
- templates/form-automation.sh 1.8 KB runs code
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.
- 5d ago First seen · 218 lines · 108 tokens per session scan A 84effb42371b
agent-browser is a skill published in the GitHub repository sumulige/sumulige-claude (2 stars, last pushed 6mo ago), licensed MIT. It adds 108 tokens to every session and 1,721 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to agent-browser, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
co-evolution
General-purpose co-evolution for questions, ideas, drafts, plans, specs, arguments, and markdown documents. Composes or bounces content between agents using [CONTESTED]/[CLARIFY] markers until it converges. Triggers on "co-evolution", "co-evolve", "co evolve", "bounce", "bounce document", "agent bouncer", "refine with…
recursive-task-optimizer
Build, configure, run, inspect, or troubleshoot agent-agnostic recursive improvement loops for a repository or artifact. Use when a task should be attempted repeatedly by Claude Code, Codex CLI, Hermes, or another CLI agent; when candidates must inherit mutable task instructions, a self-improving meta-procedure, and…
dev-review
Code-focused plan-bounce-execute workflow between Claude Code (Opus) and Codex CLI. Use when the user wants repo files changed, a bug fixed, a feature implemented, or a code plan verified before execution. One AI composes a plan, it bounces between agents with [CONTESTED]/[CLARIFY] markers until refined, then the…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
high-fidelity-extraction
Advanced protocol for extracting granular social media and web intelligence using browser automation and DOM analysis.
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.