AWS Agentic AI
zxkane/aws-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
Runs agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore, with credentials taken from the environment or the AWS CLI.
Install Agent-Browser on AWS AgentCore
$ npx skills add vercel-labs/agent-browser --skill agentcore -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vercel-labs/agent-browser agentcore --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skill-data/agentcore .claude/skills/agentcore && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .claude/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcoreType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vercel-labs/agent-browser --skill agentcore -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vercel-labs/agent-browser agentcore --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skill-data/agentcore .agents/skills/agentcore && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .agents/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/agent-browser --skill agentcore -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vercel-labs/agent-browser agentcore --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skill-data/agentcore .cursor/skills/agentcore && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .cursor/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vercel-labs/agent-browser.git --path skill-data/agentcore--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vercel-labs/agent-browser --skill agentcore -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vercel-labs/agent-browser agentcore --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skill-data/agentcore .gemini/skills/agentcore && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .gemini/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vercel-labs/agent-browser agentcoreInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vercel-labs/agent-browser --skill agentcore -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .github/skills && cp -r skills-src/skill-data/agentcore .github/skills/agentcore && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .github/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vercel-labs/agent-browser --skill agentcore -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vercel-labs/agent-browser agentcore --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vercel-labs/agent-browser.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skill-data/agentcore .opencode/skills/agentcore && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "agentcore" agent skill from https://github.com/vercel-labs/agent-browser/tree/main/skill-data/agentcore into .opencode/skills/agentcore/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "agentcore", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
agentcore- GitHub stars
- 44k
- Token cost
- ~1k tokens
- SKILL.md length
- 232 words
- Files
- 1
- Skills in repo
- 10
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Runs agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore, with credentials taken from the environment or the AWS CLI.
- Works in 2 steps: Environment variables… → AWS CLI fallback (aws configure…
- Running browser automation on AWS instead of the local machine
- SKILL.md covers Setup, Core Workflow, Environment Variables and Persistent Profiles, plus 5 more sections
- Calls aws; reaches us-east-1.console.aws.amazon.com; needs AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
What it does
All standard agent-browser commands work as usual; the only change is that the browser runs in an AWS Bedrock AgentCore cloud session, chosen with -p agentcore or the AGENT_BROWSER_PROVIDER variable. Credentials come from AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, with AWS_SESSION_TOKEN optional, or fall back to the AWS CLI, which supports SSO, IAM roles and named profiles.
Settings are environment variables: AGENTCORE_REGION (default us-east-1), AGENTCORE_BROWSER_ID, AGENTCORE_PROFILE_ID for a persistent profile that keeps cookies and localStorage between sessions, AGENTCORE_SESSION_TIMEOUT (default 3600 seconds) and AWS_PROFILE. A Live View URL is printed to stderr when a session starts, so you can watch it in the AWS Console. If the AWS CLI is missing, install it or set the key variables directly.
When your agent uses it
- Running browser automation on AWS instead of the local machine
- Keeping a logged-in browser profile across several sessions
- Watching a cloud browser session live from the AWS Console
Example prompts
- “Open https://app.example.com/login on an AgentCore browser and keep the profile as my-app.”
- “Run this scrape on a cloud browser in us-east-2.”
- “Use agentcore for the rest of this session by setting the provider in the environment.”
Requirements
- The agent-browser CLI
- Working AWS credentials, from environment variables or the AWS CLI
- Access to AWS Bedrock AgentCore
- Pre-approved tools (allowed-tools): Bash(agent-browser:*), Bash(npx agent-browser:*)
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, optionally AWS_SESSION_TOKEN)
- AWS CLI fallback (aws configure export-credentials), which supports SSO, IAM roles, and named profiles
What it can do on your machine
Read from SKILL.md and the folder at commit f7c8b07. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(agent-browser:*)Bash(npx agent-browser:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
aws
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
us-east-1.console.aws.amazon.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names these keys or tokens, usually read from environment variables:
AWS_ACCESS_KEY_IDAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKEN
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Agent-Browser on AWS AgentCore loads about 1k tokens when it runs. Until then it costs about 104 tokens; SKILL.md has 232 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vercel-labs/agent-browser at commit f7c8b07, republished under its Apache-2.0 licence (© vercel-labs). 232 words, ~1,002 tokens.
Download SKILL.mdSave it as
.claude/skills/agentcore/SKILL.md (or your agent's skills folder).- name
- agentcore
- description
- Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.
- allowed-tools
- Bash(agent-browser:*), Bash(npx agent-browser:*)
AWS Bedrock AgentCore
Run agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore. All standard agent-browser 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
agent-browser -p agentcore open https://example.com
# Everything else is the same as local Chrome
agent-browser snapshot -i
agent-browser click @e1
agent-browser screenshot page.png
agent-browser closeEnvironment 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 agent-browser -p agentcore open https://app.example.com/login
agent-browser snapshot -i
agent-browser fill @e1 "user@example.com"
agent-browser fill @e2 "password"
agent-browser click @e3
agent-browser close
# Future runs: already authenticated
AGENTCORE_PROFILE_ID=my-app agent-browser -p agentcore open https://app.example.com/dashboardLive 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#Region Selection
# Default: us-east-1
agent-browser -p agentcore open https://example.com
# Explicit region
AGENTCORE_REGION=eu-west-1 agent-browser -p agentcore open https://example.comCredential Patterns
# Explicit credentials (CI/CD, scripts)
export AWS_ACCESS_KEY_ID=AKIA...
export AWS_SECRET_ACCESS_KEY=...
agent-browser -p agentcore open https://example.com
# SSO (interactive)
aws sso login --profile my-profile
AWS_PROFILE=my-profile agent-browser -p agentcore open https://example.com
# IAM role / default credential chain
agent-browser -p agentcore open https://example.comUsing with AGENT_BROWSER_PROVIDER
Set the provider via environment variable to avoid passing -p agentcore on every command:
export AGENT_BROWSER_PROVIDER=agentcore
export AGENTCORE_REGION=us-east-2
agent-browser open https://example.com
agent-browser snapshot -i
agent-browser click @e1
agent-browser closeCommon Issues
"Failed to run aws CLI" means AWS CLI is not installed or not in PATH. Either install it or set AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY directly.
"AWS CLI failed: ... Run 'aws sso login'" means SSO credentials have expired. Run aws sso login to refresh them.
Session timeout: The default is 3600 seconds (1 hour). For longer tasks, increase with AGENTCORE_SESSION_TIMEOUT=7200.
© vercel-labs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skill-data/agentcore of vercel-labs/agent-browser.
Open the folder on GitHubat commit f7c8b07
Compare with similar skills
Agent-Browser on AWS AgentCore next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Agent-Browser on AWS AgentCore this skillvercel-labs/agent-browser | 44k | — | ~1k | Automated safety check: Pass | Apache-2.0 | |
| AWS Agentic AIzxkane/aws-skills | 367 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Hcls Deploy Agentaws-samples/amazon-bedrock-agents-healthcare-lifesciences | 274 | — | ~813 | Automated safety check: Pass | MIT-0 | |
| AWS Agentic AIsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| AWS Strands Agents Agentcoresammcj/agentic-coding | 162 | 1 repos | ~3k | Automated safety check: Pass | Apache-2.0 | |
| AWS Harnesshoodini/ai-agents-skills | 282 | — | ~4.2k | Automated safety check: Notes | None |
Similar skills
- Official
Hcls Deploy Agent
aws-samples/amazon-bedrock-agents-healthcare-lifesciences
A skill your agent uses when a developer wants to deploy an HCLS agent to Amazon Bedrock AgentCore, configure Gateway tools as MCP endpoints, set up authentication with Cognito, configure memory, or…
AWS Agentic AI
sickn33/agentic-awesome-skills
AWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale.
AWS Strands Agents Agentcore
sammcj/agentic-coding
A skill your agent uses when working with AWS Strands Agents SDK or Amazon Bedrock AgentCore platform for building AI agents.
AWS Harness
hoodini/ai-agents-skills
Build a new AI agent on AWS and deploy it easily, OR wrap and deploy an agent you already have, using the Amazon Bedrock AgentCore harness.
Bedrock Agentcore
majiayu000/claude-skill-registry
Amazon Bedrock AgentCore platform for building, deploying, and operating production AI agents.
More from vercel-labs/agent-browser
All 10 skills in this repo- Official
Agent Browser CLI
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…
- Official
Dogfood Exploratory QA
vercel-labs/agent-browser
Explores a web app with the agent-browser CLI to find bugs and UX problems, then writes a report with screenshots, repro videos and step-by-step reproduction for each issue.
- Official
Electron App Automation
vercel-labs/agent-browser
Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.
- Official
Slack Browser Automation
vercel-labs/agent-browser
Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.
- Official
Core Guide for agent-browser
vercel-labs/agent-browser
Core usage guide for the agent-browser CLI: the snapshot-and-ref workflow for navigating, clicking, filling forms, extracting data and running parallel sessions.
- Official
Derive API Client from Browser Traffic
vercel-labs/agent-browser
Records a site's browser traffic into a HAR file, then builds a standalone client or CLI that calls its internal endpoints directly with no browser.
Related
Works with
Categories
Questions about Agent-Browser on AWS AgentCore
What does Agent-Browser on AWS AgentCore do?
Runs agent-browser on cloud browser sessions hosted by AWS Bedrock AgentCore, with credentials taken from the environment or the AWS CLI. All standard agent-browser commands work as usual; the only change is that the browser runs in an AWS Bedrock AgentCore cloud session, chosen with -p agentcore or the AGENT_BROWSER_PROVIDER variable. Credentials come from AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY, with AWS_SESSION_TOKEN optional, or fall back to the AWS CLI, which supports SSO, IAM roles and named profiles.
When should I use Agent-Browser on AWS AgentCore?
Agent-Browser on AWS AgentCore fits situations like: running browser automation on AWS instead of the local machine; keeping a logged-in browser profile across several sessions; watching a cloud browser session live from the AWS Console.
How do I install Agent-Browser on AWS AgentCore in Claude Code?
Run `npx skills add vercel-labs/agent-browser --skill agentcore -a claude-code`. Or copy the skill folder (skill-data/agentcore in vercel-labs/agent-browser) into .claude/skills/agentcore in your project. Claude Code loads it when a task matches its description.
How do I install Agent-Browser on AWS AgentCore in Codex?
Run `npx skills add vercel-labs/agent-browser --skill agentcore -a codex`. Or copy the skill folder (skill-data/agentcore in vercel-labs/agent-browser) into .agents/skills/agentcore in your project. Codex loads it when a task matches its description.
Can I use Agent-Browser on AWS AgentCore in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vercel-labs/agent-browser --skill agentcore -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agentcore, .gemini/skills/agentcore, .github/skills/agentcore and .opencode/skills/agentcore in your project.
What does Agent-Browser on AWS AgentCore need to run?
Going by SKILL.md and its folder, Agent-Browser on AWS AgentCore needs the command-line tools its instructions call (aws) and credentials named AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY and AWS_SESSION_TOKEN. Our summary lists: The agent-browser CLI; Working AWS credentials, from environment variables or the AWS CLI; Access to AWS Bedrock AgentCore. Its frontmatter pre-approves these tools: Bash(agent-browser:*), Bash(npx agent-browser:*).
Does Agent-Browser on AWS AgentCore access the network?
SKILL.md names 1 domain. In commands or code: us-east-1.console.aws.amazon.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Agent-Browser on AWS AgentCore safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Agent-Browser on AWS AgentCore use?
Agent-Browser on AWS AgentCore is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Agent-Browser on AWS AgentCore use?
About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Agent-Browser on AWS AgentCore?
Skills that share tags, products or a category with Agent-Browser on AWS AgentCore: AWS Agentic AI (zxkane/aws-skills, 367 stars), Hcls Deploy Agent (aws-samples/amazon-bedrock-agents-healthcare-lifesciences, 274 stars), AWS Agentic AI (sickn33/agentic-awesome-skills, 47k stars) and AWS Strands Agents Agentcore (sammcj/agentic-coding, 162 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Agent-Browser on AWS AgentCore?
vercel-labs (a GitHub organization, an official publisher) maintains it in vercel-labs/agent-browser, which has 43,581 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on October 6, 2026.
Source: vercel-labs/agent-browser on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.