Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/zhu1090093659/codeconductor/agent-browsernpx skills add zhu1090093659/CodeConductor --skill agent-browsergit clone --depth 1 https://github.com/zhu1090093659/CodeConductorWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/zhu1090093659/codeconductor/agent-browser)<a href="https://agentmods.dev/skills/zhu1090093659/codeconductor/agent-browser"><img src="https://agentmods.dev/badge/skills/zhu1090093659/codeconductor/agent-browser.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00056 | $0.01088 |
| Opus 5 | $0.00028 | $0.00544 |
| Sonnet 5 | $0.00011 | $0.00218 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
agent-browser scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Browser
Overview
Use agent-browser to automate web UI tasks from CodeConductor. Prefer /browser <args> to execute commands through the built-in integration.
Quick start
- Navigate:
/browser open https://example.com - Snapshot:
/browser snapshot - Act using refs or selectors (click, fill, type).
- Validate with
getoriscommands. - Capture
screenshotortraceif needed. closewhen done.
Workflow
- Define the target URL, required outputs, and authentication needs.
- Set viewport/device/headers/credentials when required.
- Use
snapshotorfindcommands to locate elements deterministically. - Use
waitto stabilize before actions. - Execute actions in small steps and validate with
getoris. - Save artifacts (screenshot, state, trace) only when needed.
- Close the browser.
Selector and waiting guidance
- Prefer refs from
snapshotoutput for deterministic targeting. - Use semantic locators:
find role,find label,find text,find placeholder,find testid. - Use
waitfor elements, text, URL patterns, or network idle before actions.
Command reference (all supported)
Core
agent-browser open <url>
agent-browser click <sel>
agent-browser dblclick <sel>
agent-browser fill <sel> <text>
agent-browser type <sel> <text>
agent-browser press <key>
agent-browser hover <sel>
agent-browser select <sel> <val>
agent-browser check <sel>
agent-browser uncheck <sel>
agent-browser scroll <dir> [px]
agent-browser screenshot [path]
agent-browser snapshot
agent-browser eval <js>
agent-browser close
Get info
agent-browser get text <sel>
agent-browser get html <sel>
agent-browser get value <sel>
agent-browser get attr <sel> <attr>
agent-browser get title
agent-browser get url
agent-browser get count <sel>
agent-browser get box <sel>
Check state
agent-browser is visible <sel>
agent-browser is enabled <sel>
agent-browser is checked <sel>
Find elements
agent-browser find role <role> <action> [value]
agent-browser find text <text> <action>
agent-browser find label <label> <action> [value]
agent-browser find placeholder <ph> <action> [value]
agent-browser find testid <id> <action> [value]
agent-browser find first <sel> <action> [value]
agent-browser find nth <n> <sel> <action> [value]
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 178 lines · 56 tokens per session scan A 00640952261c
agent-browser is a skill published in the GitHub repository zhu1090093659/CodeConductor (80 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,088 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.
traceway-setup
Analyze and instrument repositories for Traceway observability. Use when the user wants to plan, add, migrate, or verify Traceway or OpenTelemetry monitoring for backend, browser, full-stack, mobile or iOS, or AI-agent software, including project topology and user-approved setup-plan creation. Backends use OTLP/HTTP…