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/maddada/ghostex/ghostex-browser-usenpx skills add maddada/Ghostex --skill ghostex-browser-usegit clone --depth 1 https://github.com/maddada/GhostexWrote 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/maddada/ghostex/ghostex-browser-use)<a href="https://agentmods.dev/skills/maddada/ghostex/ghostex-browser-use"><img src="https://agentmods.dev/badge/skills/maddada/ghostex/ghostex-browser-use.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.00090 | $0.01542 |
| Opus 5 | $0.00045 | $0.00771 |
| Sonnet 5 | $0.00018 | $0.00308 |
| Haiku 4.5 | $0.00009 | $0.00154 |
Grade A, and why
ghostex-browser-use 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghostex-browser-use
Use Trycua's typed browser workflow for supported browser page content. Keep the browser bound to an exact native window and verify every mutation from a fresh semantic snapshot.
If $cua-driver is available, load it and read its BROWSER.md before acting;
that versioned skill is the source of truth for the installed driver's schemas,
authorization rules, and platform support.
Use the cua-driver CLI, not MCP. Do not configure, register, or invoke a
Trycua MCP server for this workflow.
Route the task
- Use this skill for page content in supported Chrome, Chromium, Edge, and exactly correlated Electron surfaces.
- Use
$ghostex-embedded-browser-usefor Ghostex's built-in CEF browser panes. - Use
$ghostex-computer-usefor browser chrome, native prompts and dialogs, Safari, Firefox, or a surface that Trycua cannot bind exactly. - Prefer an application API, connector, or CLI when the requested result does not require browser UI interaction.
Check readiness
Run read-only checks before starting:
which cua-driver
cua-driver status
cua-driver check_permissions '{"prompt":false}'
cua-driver list-tools
If the daemon is not running on macOS, start the signed app in the background:
open -n -g -a CuaDriver --args serve
Use CLI calls in the form cua-driver <tool> '<JSON>'.
Windows and WSL
On Windows, Trycua installs on the Windows side. A Ghostex agent session runs
inside the WSL distribution, where there is no Linux cua-driver binary, so
which cua-driver failing there does not mean Trycua is missing. Call it across
the interop boundary through powershell.exe instead:
powershell.exe -NoProfile -Command "cua-driver status"
powershell.exe -NoProfile -Command "cua-driver list-tools"
powershell.exe -NoProfile -Command "cua-driver start_session '{\"session\":\"browser-run-1\",\"capture_scope\":\"window\"}'"
The general form is powershell.exe -NoProfile -Command "cua-driver <tool> '<JSON>'". Inside a bash double-quoted string, escape the JSON's own double
quotes as \"; PowerShell then hands the single-quoted JSON to Trycua as one
argument.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 161 lines · 90 tokens per session scan A 925b0b3f9e65
ghostex-browser-use is a skill published in the GitHub repository maddada/Ghostex (753 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 1,542 once invoked, about $0.0005 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.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…
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.