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/leeguooooo/chrome-use/agentcorenpx skills add leeguooooo/chrome-use --skill agentcoregit clone --depth 1 https://github.com/leeguooooo/chrome-useWhat 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.00089 | $0.00954 |
| Opus 5 | $0.00044 | $0.00477 |
| Sonnet 5 | $0.00018 | $0.00191 |
| Haiku 4.5 | $0.00009 | $0.00095 |
Grade A, and why
agentcore 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 yesterday.
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
94% identical to agentcore — 48 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Bedrock AgentCore
Run chrome-use on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard chrome-use commands work identically; the only difference is where the browser runs.
Setup
Credentials are resolved automatically:
- Environment variables (
AWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY, optionallyAWS_SESSION_TOKEN) - AWS CLI fallback (
aws configure export-credentials), which supports SSO, IAM roles, and named profiles
No additional setup is needed if the user already has working AWS credentials.
Core Workflow
# Open a page on an AgentCore cloud browser
chrome-use -p agentcore open https://example.com
# Everything else is the same as local Chrome
chrome-use snapshot -i
chrome-use click @e1
chrome-use screenshot page.png
chrome-use close
Environment Variables
| Variable | Description | Default |
|---|---|---|
AGENTCORE_REGION |
AWS region | us-east-1 |
AGENTCORE_BROWSER_ID |
Browser identifier | aws.browser.v1 |
AGENTCORE_PROFILE_ID |
Persistent browser profile (cookies, localStorage) | (none) |
AGENTCORE_SESSION_TIMEOUT |
Session timeout in seconds | 3600 |
AWS_PROFILE |
AWS CLI profile for credential resolution | default |
Persistent Profiles
Use AGENTCORE_PROFILE_ID to persist browser state across sessions. This is useful for maintaining login sessions:
# First run: log in
AGENTCORE_PROFILE_ID=my-app chrome-use -p agentcore open https://app.example.com/login
chrome-use snapshot -i
chrome-use fill @e1 "[email protected]"
chrome-use fill @e2 "password"
chrome-use click @e3
chrome-use close
# Future runs: already authenticated
AGENTCORE_PROFILE_ID=my-app chrome-use -p agentcore open https://app.example.com/dashboard
Live View
When a session starts, AgentCore prints a Live View URL to stderr. Open it in a browser to watch the session in real time from the AWS Console:
Session: abc123-def456
Live View: https://us-east-1.console.aws.amazon.com/bedrock-agentcore/browser/aws.browser.v1/session/abc123-def456#
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.
- yesterday First seen · 116 lines · 89 tokens per session scan A f4cac08a70a2
agentcore is a skill published in the GitHub repository leeguooooo/chrome-use (156 stars, last pushed 2d ago), licensed Apache-2.0. It adds 89 tokens to every session and 954 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to agentcore, differing in 48 lines, and is treated as a copy.
Other skills, from other repositories
browseweave
Use when installing, repairing, verifying, diagnosing, or safely operating the BrowseWeave systemd-based Linux developer preview with Chrome, Zen, or Firefox and a local MCP client. Do not use for store publication or bypassing site protections.
ultimate-playwright
Browser automation via ultimate-playwright-mcp. Use when the agent needs to control a shared Chrome browser — open tabs, navigate, click, type, fill forms, take snapshots. Handles multi-user tab group isolation so multiple sessions can share one browser without interference. Use for web browsing, scraping, form…
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
surf-codebase
Navigate and modify surf-cli codebase - Chrome extension + native host for AI browser automation. Use for surf-cli code work, architecture questions, implementing browser control/CDP/accessibility/network features.
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…