agentmods.dev

opencli-browser-sitemap

opencli-browser-sitemap is a skill for Claude Code from mxyhi/ok-skills. It costs 64 tokens per session (880 once invoked), scanned A, a copy of opencli-browser-sitemap, Apache-2.0.

A guide for using sitemap notes while controlling a website through OpenCLI’s browser commands. A sitemap is an agent-oriented map of known pages, actions, and workflows.

In plain words
What is it for?
Use it to choose known workflows, inspect only relevant sitemap files, check the page after actions, and recover when the site differs from the notes.
Why use it?
It reduces blind navigation while keeping the live browser page as the source of truth when saved notes are outdated.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

not rated 485repo +4 3d ago A scan 64 tokens copy · 100% Apache-2.0

Good fit Use it to choose known workflows, inspect only relevant sitemap files, check the page after actions, and recover when the site differs from the notes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mxyhi/ok-skills/opencli-browser-sitemap
View source ↗ mxyhi/ok-skills
Install

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.

Any agent
npx skills add mxyhi/ok-skills --skill opencli-browser-sitemap
Clone the repo
git clone --depth 1 https://github.com/mxyhi/ok-skills

Made for: Claude Code.

Wrote 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.

agentmods badge for opencli-browser-sitemap

README.md
[![agentmods](https://agentmods.dev/badge/skills/mxyhi/ok-skills/opencli-browser-sitemap/github.svg)](https://agentmods.dev/skills/mxyhi/ok-skills/opencli-browser-sitemap)
Your own site
<a href="https://agentmods.dev/skills/mxyhi/ok-skills/opencli-browser-sitemap"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/opencli-browser-sitemap/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for opencli-browser-sitemap

Your own site · 80×15
<a href="https://agentmods.dev/skills/mxyhi/ok-skills/opencli-browser-sitemap"><img src="https://agentmods.dev/badge/skills/mxyhi/ok-skills/opencli-browser-sitemap.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 880 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00064 $0.00880
Opus 5 $0.00032 $0.00440
Sonnet 5 $0.00013 $0.00176
Haiku 4.5 $0.00006 $0.00088

Measured 12d ago against content hash 71ebf47c5078, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

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 12d 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.

Origin

This is a copy

100% identical to opencli-browser-sitemap — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

opencli/opencli-browser-sitemap/SKILL.md · 97 lines

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

  1. Run or reuse opencli browser <session> state to know the current page.
  2. Read only the smallest relevant sitemap files:
    • SITE.md for site-level orientation.
    • One matching pages/<page-id>.md for current state.
    • One matching workflows/<task-id>.md for the user goal.
    • pitfalls.md only when blocked or warned by the workflow.
  3. Prefer the workflow's Best path. If it names an adapter such as opencli twitter post, use that before raw browser actions.
  4. If the adapter is unavailable or fails, use the Fallback path browser workflow.
  5. After each navigation or state-changing action, refresh state and compare the workflow's state_signature.
  6. If reality disagrees, trust reality, continue probing, and write a local stale note or draft patch.
  7. 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 state or find with 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.

Read the full file on GitHub · 97 lines

Changes

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.

  1. 12d ago First seen · 97 lines · 64 tokens per session scan A 71ebf47c5078

Subscribe to this mod's changes

opencli-browser-sitemap is a skill published in the GitHub repository mxyhi/ok-skills (485 stars, last pushed 3d 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. It is 100% identical to opencli-browser-sitemap, differing in 0 lines, and is treated as a copy.

Browser automationClaude Codeagent-skillsagents-mdcodexcursorskills
Related

Other skills, from other repositories

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

addyosmani/agent-skills · 68 tokens

browser_cdp

Use this skill when the user explicitly wants to connect to a running Chrome browser, scan local CDP ports, specify a cdpport, or share a single browser across multiple agents/tools. By default, browseruse already launches the browser using managed CDP; if the user does not want to expose browser history, cookies, or…

agentscope-ai/skills · 84 tokens

browser_cdp

A guide for connecting browser-control tools to an existing Chrome session through its remote debugging interface. It explains scanning ports, attaching to a browser, choosing a port, sharing a browser, and switching to a more private control mode.

agentscope-ai/skills · 97 tokens

browser_visible

A guide to browseruse launch settings for Chromium-based browsers. It covers visible windows, private control, extra browser start options such as incognito mode or a proxy, and choosing a browser executable path.

agentscope-ai/skills · 96 tokens

browser_visible

Use this skill when the user needs to control the browser launch mode for browseruse. By default, browseruse launches the local Chrome/Chromium using managed CDP; headed controls whether the window is visible, and privatemode controls whether CDP is disabled in favor of Playwright.

agentscope-ai/skills · 64 tokens

awesome-content-publisher

Publishes a prepared batch of scheduled posts to the user's own accounts through their live browser (Playwright MCP bridge): bridge and format preflights, per-platform login checks that never automate a login, a persistent ledger that prevents duplicate posts across restarts, timezone-mapped scheduling that can idle…

khasky/awesome-agent-skills · 148 tokens