agentleFS
Sign inStart free
leaf76leaf76/agent-skills/hermes-chrome/SKILL.md

hermes-chrome

Skill0 starsChanged 3 months agoMITView on GitHub

Drive the user's daily Chrome via Hermes Chrome (extension + local bridge :19876 + CLI). Use for real cookies/SSO, workspace tabs, capture, cookie-aware download, local URL/file safety checks, light DOM ops without hijacking the active tab. Prefer over headless when live daily Chrome is required.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not osascript / tell Google Chrome to activate

    line 23
  2. Distinctive:

    Do not rewrite the user's active tab

    line 24
  3. Very specific:

    Prefer check-url before download.

    line 27
  4. Distinctive:

    No cloud threat APIs by default

    line 28
  5. Very specific:

    If ping version lags repo, tell user: Reload unpacked/CWS + click icon.

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Hermes Chrome (Grok skill)

When to use

  • Need user's real Chrome cookies / SSO / already-open tabs
  • Logged-in capture, SSO smoke, already-open workspace tabs
  • Download with cookie jar, local URL/file safety checks
  • User says hermes-chrome / daily Chrome / bridge 19876

When NOT to use

  • Public pages with no login → Hermes headless browser_* / Playwright headless
  • Own-app E2E / layout → Chrome DevTools MCP / Playwright / browser-e2e
  • Isolated headed browser without daily cookies → Agent Chrome :9333

Hard rules

  • Do not osascript / tell Google Chrome to activate
  • Do not rewrite the user's active tab
  • Fail-fast: if ping times out once, stop the chain; ask user to Reload + click icon
  • Gate with health: prefer extension_connected: true on /v1/health
  • Prefer check-url before download; do not --force block findings without user ask
  • No cloud threat APIs by default

Paths

PiecePath
CLI~/.hermes/scripts/hermes-chrome.sh or repo scripts/hermes-chrome.sh
Repolocal Hermes Chrome checkout (CLI usually under ~/.hermes/scripts/)
Bridgehttp://127.0.0.1:19876
Runtime~/.hermes/run/hermes-chrome/
Downloads~/.hermes/run/hermes-chrome/downloads/

Ops loop

CLI=~/.hermes/scripts/hermes-chrome.sh

# 1) Bridge
$CLI bridge-status
# extension_connected should be true; if bridge down: $CLI install-launchd  or bridge-start

# 2) Extension gate (fail-fast)
$CLI ping
# expect: "extension":"hermes-chrome","version":"1.4.1"+ 

# 3) Work
$CLI start 'https://example.com/'
$CLI list-tabs --group
$CLI navigate 'https://example.org/' --tab-id <id>
$CLI capture --prefer active --out /tmp/page.png
$CLI eval --tab-id <id> --expr 'document.title'
$CLI page-assets --tab-id <id>
$CLI check-tab-links --tab-id <id>
$CLI --json ping
$CLI check-url 'https://example.com/report.pdf'
$CLI download 'https://example.com/report.pdf'            # direct
$CLI download 'https://app.example/private' --cookies     # cookie jar
$CLI analyze ~/.hermes/run/hermes-chrome/downloads/report.pdf
$CLI status
$CLI stop   # closes Hermes workspace tabs

Capture / download notes

  • captureVisibleTab may briefly activate the target tab; put capture targets in a separate window when possible
  • Optional title filters can target known window titles; do not hardcode product-specific symbols
  • download runs check → save → analyze unless --no-check / --no-analyze / --force
  • analyze is local heuristics (not antivirus)

Version gate

VersionCapability
1.2.0+capture, list-tv
1.3.0+list-tabs, navigate, eval, click, type, health extension_last_seen
1.4.1+fetch_url (cookies download), page-assets, CLI check-url/download/analyze

If ping version lags repo, tell user: Reload unpacked/CWS + click icon.

Install / recovery

$CLI install-help
$CLI install-launchd    # macOS login + KeepAlive
# chrome://extensions → Load unpacked → <repo>/extension → click icon

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free