Menü
Run browser automation on AWS Bedrock AgentCore cloud browsers or AWS-hosted sessions.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
1Password CLI (op) でサインイン・vault 確認・secret 注入を行う時に使う。Claude セッションでは service account token (OP_SERVICE_ACCOUNT_TOKEN) をtoken ファイル (~/.config/op/service-account-token) から直前注入する方式を使い、op read の stdout を Claude context に流さない方針を強制する。「op signin」「op service-account」「op read」「op run」「op inject」「1Password から取って」などで発火。
Browser automation for opening sites, forms, clicks, screenshots, scraping, login, and web app testing.
Capture architecture decisions as ADRs with context, alternatives, and rationale.
不具合修正のワークフロー（調査→再現→修正→検証）を controller がオーケストレーションするための指揮書。バグ・不具合・障害の修正で使う。explorer で原因特定、implementer で再現テスト→修正、verifier で検証。「バグを直して」「不具合修正」「この障害を調査して直す」などで参照。
Create CodeTour `.tour` walkthroughs with file/line anchors.
Analyze a codebase and create an onboarding guide with architecture, entry points, conventions, and starter CLAUDE.md.
Basierend auf der SOC-Berufsklassifikation
| name | agentcore |
| description | Run browser automation on AWS Bedrock AgentCore cloud browsers or AWS-hosted sessions. |
| allowed-tools | Bash(agent-browser:*), Bash(npx agent-browser:*) |
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.
Credentials are resolved automatically:
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, optionally AWS_SESSION_TOKEN)aws configure export-credentials), which supports SSO, IAM roles, and named profilesNo additional setup is needed if the user already has working AWS credentials.
# 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 close
| 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 |
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/dashboard
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#
# 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.com
# 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.com
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 close
"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.