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/unclutter-pro/atlas/browsernpx skills add unclutter-pro/atlas --skill browsergit clone --depth 1 https://github.com/unclutter-pro/atlasWrote 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/unclutter-pro/atlas/browser)<a href="https://agentmods.dev/skills/unclutter-pro/atlas/browser"><img src="https://agentmods.dev/badge/skills/unclutter-pro/atlas/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 | $0.00107 | $0.02997 |
| Opus 5 | $0.00053 | $0.01499 |
| Sonnet 5 | $0.00021 | $0.00599 |
| Haiku 4.5 | $0.00011 | $0.00300 |
Grade A, and why
browser scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -H "Authorization: Bearer $(cat ~/secrets/api_key)" https://api.example.com How it starts
The opening of the file, as written. The whole thing — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with browser
The browser CLI uses Chrome/Chromium via CDP directly. It is powered by agent-browser.
Core Workflow
Every browser automation follows this pattern:
- Navigate:
browser open <url> - Snapshot:
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
browser open https://example.com/form
browser snapshot -i
# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit"
browser fill @e1 "[email protected]"
browser fill @e2 "password123"
browser click @e3
browser wait --load networkidle
browser snapshot -i # Check result
Command Chaining
Commands can be chained with && in a single shell invocation. The browser persists between commands via a background daemon, so chaining is safe and more efficient than separate calls.
# Chain open + wait + snapshot in one call
browser open https://example.com && browser wait --load networkidle && browser snapshot -i
# Chain multiple interactions
browser fill @e1 "[email protected]" && browser fill @e2 "password123" && browser click @e3
# Navigate and capture
browser open https://example.com && browser wait --load networkidle && browser screenshot page.png
When to chain: Use && when you don't need to read the output of an intermediate command before proceeding (e.g., open + wait + screenshot). Run commands separately when you need to parse output between steps (e.g., snapshot to discover refs, then interact using those refs).
Handling Authentication
When automating a site that requires login, choose the approach that fits:
Option 1: Import auth from the user's browser (fastest for one-off tasks)
browser --auto-connect state save ./auth.json
browser --state ./auth.json open https://app.example.com/dashboard
Option 2: Persistent profile (simplest for recurring tasks)
What ships with it
10 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 7.8 KB
- references/commands.md 10 KB
- references/profiling.md 3.2 KB
- references/proxy-support.md 4.7 KB
- references/session-management.md 4.0 KB
- references/snapshot-refs.md 5.1 KB
- references/video-recording.md 3.2 KB
- templates/authenticated-session.sh 3.5 KB runs code
- templates/capture-workflow.sh 1.7 KB runs code
- templates/form-automation.sh 1.7 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.
- 3d ago First seen · 379 lines · 107 tokens per session scan A 7e95bcb8619e
browser is a skill published in the GitHub repository unclutter-pro/atlas (2 stars, last pushed 15d ago), licensed MIT. It adds 107 tokens to every session and 2,997 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.