agent-browser
Browser Automation with agent-browser
Core Workflow
Every browser automation follows this pattern:
- Navigate:
agent-browser open <url> - Snapshot:
agent-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
agent-browser open https://example.com/form
agent-browser snapshot -i
# Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit"
agent-browser fill @e1 "user@example.com"
agent-browser fill @e2 "password123"
agent-browser click @e3
More from chandima/opencode-config
github-ops
|
2context7-docs
|
2mcporter
Direct MCP access via MCPorter. Use to discover MCP servers, list MCP tools, or call an MCP tool (e.g., chrome-devtools screenshot, firecrawl scrape) when no specific skill exists. Supports any configured MCP server.
1asu-discover
Semantic search across 760+ ASU GitHub repositories via RAG. Use for finding code patterns, integrations, SDKs, and ASU-specific conventions. Domains: PeopleSoft, EDNA, DPL, Terraform, EEL, Vault, CI/CD. Use BEFORE starting ASU integration tasks.
1skill-evals-run
Run the OpenCode skill-loading eval suite for this repo. Use when asked to run skill evals, skill-loading evals, or the skill-evals-run command.
1planning-doc
Create or update PLAN.md planning documents when users ask for a plan or planning. Use when asked to create a plan, planning document, or plan-based workflow.
1