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/jackwener/opencli/opencli-browser-sitemapnpx skills add jackwener/OpenCLI --skill opencli-browser-sitemapgit clone --depth 1 https://github.com/jackwener/OpenCLIWhat 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.00064 | $0.00880 |
| Opus 5 | $0.00032 | $0.00440 |
| Sonnet 5 | $0.00013 | $0.00176 |
| Haiku 4.5 | $0.00006 | $0.00088 |
Grade A, and why
opencli-browser-sitemap 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- opencli-browser-sitemap — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
opencli-browser-sitemap
Use this skill when opencli browser open or opencli browser analyze reports sitemap.available: true, or when the user asks you to use a site's sitemap.
The sitemap is prior knowledge, not ground truth. It should reduce blind clicking, but it must never override the live browser state.
Consumption Loop
- Run or reuse
opencli browser <session> stateto know the current page. - Read only the smallest relevant sitemap files:
SITE.mdfor site-level orientation.- One matching
pages/<page-id>.mdfor current state. - One matching
workflows/<task-id>.mdfor the user goal. pitfalls.mdonly when blocked or warned by the workflow.
- Prefer the workflow's Best path. If it names an adapter such as
opencli twitter post, use that before raw browser actions. - If the adapter is unavailable or fails, use the Fallback path browser workflow.
- After each navigation or state-changing action, refresh
stateand compare the workflow'sstate_signature. - If reality disagrees, trust reality, continue probing, and write a local stale note or draft patch.
- If an action recovery includes
adapter_health_update: <adapter> -> suspect|broken, update the local overlay workflow that references that adapter so future agents go straight to the fallback path.
Lookup Order
Read local overlay first, then global seed:
~/.opencli/sites/<site>/sitemap/ # local overlay
sitemaps/<site>/ # repo seed (top-level)
Local files override global files with the same stable id.
Do not load an entire large sitemap into context. If the directory is large, list filenames first and then read only the page/workflow you need.
Trust Reality Rule
If sitemap says a button, URL, route, or API should exist but the browser does not show it:
- Re-run
stateorfindwith semantic anchors. - Check whether login, locale, viewport, A/B test, or route state differs.
- Follow the real page if a safe path is visible.
- Mark the sitemap item stale in local overlay.
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.
- 2d ago First seen · 97 lines · 64 tokens per session scan A 71ebf47c5078
opencli-browser-sitemap is a skill published in the GitHub repository jackwener/OpenCLI (28,850 stars, last pushed 2d ago), licensed Apache-2.0. It adds 64 tokens to every session and 880 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
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.
remote-browser
Controls an isolated Browser Use Cloud browser from a sandboxed machine with the current Browser Use CLI.
cloud
Documentation reference for using Browser Use Cloud — the hosted API and SDK for browser automation. Use this skill whenever the user needs help with the Cloud REST API (v2, v3, or v4), browser-use-sdk (Python or TypeScript), X-Browser-Use-API-Key authentication, cloud sessions, browser profiles, profile sync, CDP…
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
qa
QA-test a website or web app and return a 1-5 quality score (5 = flawless, 1 = broken) with evidence. Use when the user wants to test, QA, evaluate, score, or "check how good" a site, page, flow, or app — including a local dev server (e.g. "qa test localhost:5173", "does the checkout work?", "rate this landing page").…
interceptor-research
Deep web-research methodology for the interceptor browser surface — investigate a topic the way researchers, intelligence analysts, investigative journalists, private investigators, and OSINT operators do, not 'read 3 links and summarize.' Use when the task is research, deep research, investigate, go deeper, be…