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/teamniteo/hakuto/agent-browsernpx skills add teamniteo/hakuto --skill agent-browsergit clone --depth 1 https://github.com/teamniteo/hakutoWrote 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/teamniteo/hakuto/agent-browser)<a href="https://agentmods.dev/skills/teamniteo/hakuto/agent-browser"><img src="https://agentmods.dev/badge/skills/teamniteo/hakuto/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 | $0.00084 | $0.02312 |
| Opus 5 | $0.00042 | $0.01156 |
| Sonnet 5 | $0.00017 | $0.00462 |
| Haiku 4.5 | $0.00008 | $0.00231 |
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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with agent-browser
Prerequisites
If agent-browser is missing from $PATH, install it globally and run the one-time Chrome download:
bun install -g agent-browser
agent-browser install # Downloads Chrome for Testing (first run only)
Alternatives: npm install -g agent-browser, brew install agent-browser, or cargo install agent-browser — each followed by agent-browser install. Surface any install failures to the user rather than improvising workarounds.
Daemon lifecycle
agent-browser runs as a background daemon that persists after the skill exits, keeping a headless Chrome alive so subsequent commands are instant. By default it never shuts down on its own, so an unused daemon can linger across projects (sometimes surfacing as a blank Chrome window on macOS, since --headless=new still spawns a real window in some configurations).
Two ways to keep it tidy:
- Auto-shutdown after idle (recommended) — set
AGENT_BROWSER_IDLE_TIMEOUT_MSin your shell environment, e.g.export AGENT_BROWSER_IDLE_TIMEOUT_MS=300000for a 5-minute idle timeout. The daemon exits N ms after the last command. - Manual cleanup — run
agent-browser close --allwhen you're done, orpkill -f agent-browserto nuke any orphans.
Why refs over selectors
The core pattern is snapshot → ref → act. Refs (@e1, @e2) come from the snapshot's accessibility tree and survive minor DOM mutations between actions; CSS selectors and XPath break easily on re-renders, dynamic class names, or hydration. Re-snapshot whenever the page navigates or the DOM changes meaningfully.
Quick start
agent-browser open <url> # Navigate to page
agent-browser snapshot -i # Get interactive elements with refs
agent-browser click @e1 # Click element by ref
agent-browser fill @e2 "text" # Fill input by ref
agent-browser close # Close browser
Core workflow
- Navigate:
agent-browser open <url> - Snapshot:
agent-browser snapshot -i(returns elements with refs like@e1,@e2) - Interact using refs from the snapshot
- Re-snapshot after navigation or significant DOM changes
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 · 273 lines · 84 tokens per session scan A 752330313b59
agent-browser is a skill published in the GitHub repository teamniteo/hakuto (5 stars, last pushed 8d ago), licensed MIT. It adds 84 tokens to every session and 2,312 once invoked, about $0.0004 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
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…
feature-walkthrough
Autonomously test the running binance-trading-bot app in a real browser. The agent drives the browser itself via the Playwright MCP - logs in, looks at each screen, and works through every feature end-to-end like a real operator, finding and fixing bugs. Use when asked to test the app, smoke-test or walk through the…
playwright-screen-recording
Record browser test videos with Playwright for PR review and bug fix verification.
browser-smoke-review
Use browser automation to review docs pages, preview URLs, rendered output, or web-facing fallow surfaces. Use when the user wants a screenshot-based review, browser smoke test, docs site check, or preview deployment inspection.
web-preview
Flutter Web版をビルド → サーバー起動 → Playwright でアクセス確認 → URLをユーザーに案内する。.
login-flows
Common login automation patterns for web apps using Playwright.