القائمة
Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
Stages all changes and generates a lean Conventional Commits message via caveman-commit — user reviews and commits manually. Triggers on any commit intent: "commit", "stage my changes", "ready to push", "let's commit", "make a commit", "commit this", "push changes", "squash and commit", or any variation. Use whenever the user signals they're done with changes and ready to commit, even if they don't mention "message" or "caveman". Does NOT run git commit — outputs a ready-to-run command for the user to execute after review.
Autonomous ML research - agent modifies GPT training code, runs 5-min experiments, keeps improvements
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
AI spend analytics — see where your token budget goes by task, model, tool, and project across 31 AI coding tools including Claude Code. Use when the user asks about AI costs, token usage, spend breakdown, or wants to optimize their AI budget.
A standalone adversarial PLAN-review loop where Claude Code (builder) and OpenAI Codex (read-only critic) tag-team an implementation plan before any code is written. Use this when you ALREADY have a plan or a clear idea and just want the cross-model stress-test — no requirements interview first. Claude drafts/loads the plan into PLAN.md, Codex reviews it in a read-only sandbox and returns VERDICT:APPROVED or VERDICT:REVISE, Claude revises and re-submits to the SAME Codex session (context preserved) until APPROVED or a configurable MAX_ROUNDS cap is hit. Human approves the converged plan before code. Use when the user says "/codex-review", "codex review my plan", "have Codex review my plan", "argue this plan with Codex", "adversarial plan review", "make Claude and Codex argue/fight over the plan", or is about to build something high-stakes (auth, schema, concurrency, migrations, payments) and wants a second-model sanity check on the PLAN before implementation. For a guided requirements interview BEFORE the rev
| name | browser-harness |
| description | Always use browser-harness for any web interaction: automation, scraping, testing, or site/app work. |
Direct browser control via CDP. For task-specific edits, use agent-workspace/agent_helpers.py. For setup, install, or connection problems, read https://github.com/browser-use/browser-harness/blob/main/install.md.
Domain skills are off by default. Set BH_DOMAIN_SKILLS=1 to enable them; see the bottom section.
If BH_DOMAIN_SKILLS=1 and the task is site-specific, read every file in the matching $BH_AGENT_WORKSPACE/domain-skills/<site>/ directory before inventing an approach.
browser-harness <<'PY'
print(page_info())
PY
browser-harness. Use heredocs for multi-line commands.run.py calls ensure_daemon() before exec.new_tab(url), not goto_url(url).If the daemon cannot connect, run diagnostics:
browser-harness --doctor
If Chrome remote debugging is not enabled, the harness opens:
chrome://inspect/#remote-debugging
Ask the user to tick "Allow remote debugging for this browser instance" and click Allow if Chrome shows a permission popup. Then retry the same browser-harness command.
Use Browser Use cloud for headless servers, parallel sub-agents, or isolated work. Authenticate once:
browser-harness auth login
Or import a key safely:
browser-harness auth login --api-key-stdin
Pick a short made-up name; r7k2 below is just a placeholder:
browser-harness <<'PY'
start_remote_daemon("r7k2")
PY
BU_NAME=r7k2 browser-harness <<'PY'
new_tab("https://example.com")
print(page_info())
PY
When the task is done and a cloud browser is still running, ask directly: "Should I close this browser now?" If yes, run stop_remote_daemon(name). Remote daemons bill until they stop or time out.
Do not start a remote daemon and then keep using the default daemon. Use the same name for BU_NAME.
Cloud profile cookie sync reference: https://github.com/browser-use/browser-harness/blob/main/interaction-skills/profile-sync.md.
capture_screenshot() to understand visible state.click_at_xy(x, y) -> screenshot again.wait_for_load().ensure_real_tab().js(...) for DOM inspection or extraction when coordinates are the wrong tool.cdp("Domain.method", ...).If you get stuck on a browser mechanic, check https://github.com/browser-use/browser-harness/tree/main/interaction-skills.
BU_NAME, BU_CDP_URL, BU_CDP_WS, or start_remote_daemon(...).$BH_AGENT_WORKSPACE/agent_helpers.py.chrome://inspect/#remote-debugging must be enabled for local Chrome control.BU_CDP_URL is an HTTP DevTools endpoint; the daemon resolves it to WebSocket.stop_remote_daemon(name) or PATCH /browsers/{id} {"action":"stop"}.Only applies when BH_DOMAIN_SKILLS=1. Otherwise ignore domain skills.
When enabled, search $BH_AGENT_WORKSPACE/domain-skills/<host>/ before inventing an approach. goto_url(...) returns up to 10 skill filenames for the navigated host.