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 skills add zxfccmm4/Obsidian-OpenCode-Knowledge --skill opencli-browsergit clone --depth 1 https://github.com/zxfccmm4/Obsidian-OpenCode-KnowledgeWrote 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/zxfccmm4/obsidian-opencode-knowledge/opencli-browser)<a href="https://agentmods.dev/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-browser"><img src="https://agentmods.dev/badge/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-browser/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.
<a href="https://agentmods.dev/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-browser"><img src="https://agentmods.dev/badge/skills/zxfccmm4/obsidian-opencode-knowledge/opencli-browser.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 4 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.1 | $0.00035 | $0.01274 |
| Opus 5.5 | $0.00014 | $0.00510 |
| Sonnet 5.5 | $0.00007 | $0.00255 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
opencli-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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenCLI Browser — Browser Automation for AI Agents
Control Chrome step-by-step via CLI. Reuses existing login sessions — no passwords needed.
Prerequisites
opencli doctor # Verify extension + daemon connectivity
Requires: Chrome running + OpenCLI Browser Bridge extension installed.
Critical Rules
- ALWAYS use
stateto inspect the page, NEVER usescreenshot—statereturns structured DOM with[N]element indices, is instant and costs zero tokens. - ALWAYS use
click/type/selectfor interaction, NEVER useevalto click or type —eval "el.click()"bypasses scrollIntoView and CDP click pipeline. - Verify inputs with
get value, not screenshots — aftertype, runget value <index>to confirm. - Run
stateafter every page change — afteropen,click(on links),scroll, always runstate. - Chain commands aggressively with
&&— combine commands to reduce overhead. evalis read-only — useevalONLY for data extraction, never for clicking, typing, or navigating.- Minimize total tool calls — plan your sequence before acting.
- Prefer
networkto discover APIs — most sites have JSON APIs. API-based adapters are more reliable than DOM scraping.
Core Workflow
- Navigate:
opencli browser open <url> - Inspect:
opencli browser state→ elements with[N]indices - Interact: use indices —
click,type,select,keys - Wait (if needed):
opencli browser wait selector ".loaded"orwait text "Success" - Verify:
opencli browser stateoropencli browser get value <N> - Repeat: browser stays open between commands
- Save: write a JS adapter to
~/.opencli/clis/<site>/<command>.js
Commands
Navigation
opencli browser open <url> # Open URL (page-changing)
opencli browser back # Go back (page-changing)
opencli browser scroll down # Scroll (up/down, --amount N)
Inspect (free & instant)
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.
- 1mo ago First seen · 139 lines · 35 tokens per session scan A 22d774a8eea7
opencli-browser is a skill published in the GitHub repository zxfccmm4/Obsidian-OpenCode-Knowledge (300 stars, last pushed 21d ago), licensed MIT. It adds 35 tokens to every session and 1,274 once invoked, about $0.0001 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
Log a CLI in with a browser/device-code flow (aws sso, gh, glab, gcloud, …) and save the result to the keychain so later commands can request it through execute.credentials.
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.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
open-design-browser
Inspect and exercise local HTML design artifacts with the existing agent-browser CLI, including screenshots and keyboard or interaction checks. Use when rendered evidence helps author or review a design; excludes browser installation, remote services, and unrelated browser automation.