メニュー
Browser automation CLI for AI agents. Use for websites, local web apps, forms, clicks, screenshots, scraping, QA, and exploratory testing. Also applies to Electron app automation, Slack checks, cloud browsers, and local browser tasks.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | agent-browser |
| description | Browser automation CLI for AI agents. Use for websites, local web apps, forms, clicks, screenshots, scraping, QA, and exploratory testing. Also applies to Electron app automation, Slack checks, cloud browsers, and local browser tasks. |
| allowed-tools | Bash(agent-browser:*), Bash(npx agent-browser:*) |
Browser automation CLI for AI agents. Uses Chrome/Chromium via CDP directly.
Install: npm i -g agent-browser && agent-browser install
You must run agent-browser skills get <name> before running any agent-browser commands.
This file does not contain command syntax, flags, or workflows. That content is served
by the CLI and changes between versions. Guessing at commands without loading the skill
will produce incorrect or outdated invocations.
agent-browser skills get agent-browser # Required before any browser automation
agent-browser skills get <name> --full # Include references and templates
Convert an implementation, debugging, release, UI, backend, security, or research request into a concrete pass/fail acceptance checklist before code changes start. Use when Codex needs blocking success criteria, scope boundaries, verification targets, or a task note for Klimkit-managed work.
Diagnose bugs, failures, flaky behavior, broken tests, CI failures, or unexpected production signals with a reproduce-first workflow and Klimkit proof. Use when the user asks to debug, investigate, root-cause, fix a failure, or explain why behavior changed.
Interview the user relentlessly about a plan, design, architecture, product decision, workflow, or release choice until shared understanding is reached, using repo and web research to prioritize the most important unresolved questions while recording the considered question shortlist, each asked question, and each approved decision in a Klimkit task note. Use when the user asks to be grilled, stress-test a plan, resolve design branches, clarify tradeoffs, or turn vague intent into explicit decisions.
Run Klimkit's full implementation workflow for code, docs, release, configuration, UI, backend, security-sensitive, or proof-producing changes. Use when the user asks Codex to implement, fix, refactor, release, migrate, wire up, or complete non-trivial repository work with checklist, verification, reflection, and final review.
Write a concise cross-task reflection note after verification and before final review for non-trivial Klimkit work. Use when Codex should connect the current task to prior work history, patterns, risks, or future process improvements.
Check, explain, or set up Klimkit static proof-report serving for `docs/work` HTML reports and Tailscale URLs. Use as the fallback when native hosted publishing (Claude Code Artifacts, Codex Sites) is unavailable and a task needs report-server readiness, `/reports/` links, Tailscale Serve verification, or troubleshooting report visibility.