anachb
Austrian public transport (VOR AnachB) for all of Austria. Query real-time departures, search…
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
$ npx -y skills add mitsuhiko/agent-stuff --skill web-browser --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/web-browserContext preview
The summary Claude sees to decide when to auto-load this skill.
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
name: web-browser description: "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." license: Stolen from Mario
Minimal CDP tools for collaborative site exploration.
./scripts/start.js --headless # Recommended: isolated reusable profile ./scripts/start.js --headless --profile # Headless with a copy of your profile ./scripts/start.js # Visible browser window when needed ./scripts/start.js --headless --reset-profile # Clear cached profile before launch
Starts Chrome with remote debugging (default port `:9222`). **Agents should use `--headless` by default** because it is less disruptive and supports navigation, evaluation, screenshots, emulation, and logging. User extensions are disabled for headless launches; a copied profile still provides its cookies and other browser state, but extension-based features are unavailable. Headed launches continue to load extensions normally. Use headed mode only when a person needs to see or interact with the browser, such as for `pick.js`, manual authentication, or debugging a headless-specific difference.
The start script only reuses a running browser when its profile and launch settings match. Stop the running skill browser before switching between headless and headed mode. Changing the debugging port does **not** isolate the profile: startup refuses to modify a profile already used on another port and preserves Chrome's profile locks.
Profile behavior:
If Chrome is installed in a non-standard location, set:
BROWSER_BIN=/path/to/chrome ./scripts/start.js --headless
Optional debug endpoint override:
BROWSER_DEBUG_PORT=9333 ./scripts/start.js --headless
./scripts/stop.js # Stop skill Chrome on :9222 BROWSER_DEBUG_PORT=9333 ./scripts/stop.js # Stop skill Chrome on :9333 ./scripts/stop.js --all # Stop all skill Chrome instances
Works for headless and headed browsers. Only processes using the skill's cached profiles are stopped, not your regular Chrome. Shutdown preserves cookies and other cached state; it never force-kills Chrome. Stop before using `--reset-profile`.
To switch to a visible browser:
./scripts/stop.js ./scripts/start.js
./scripts/nav.js https://example.com ./scripts/nav.js https://example.com --new
Navigate current tab or open new tab.
./scripts/emulate.js --list ./scripts/emulate.js iphone-14 ./scripts/emulate.js pixel-7 --landscape ./scripts/emulate.js --reset
Set an active device emulation preference (viewport, DPR, touch, UA) for browser skill commands. Use `--reset` to clear.
Commands like `nav.js`, `eval.js`, `pick.js`, `dismiss-cookies.js`, and `screenshot.js` automatically apply the active preference.
./scripts/eval.js 'document.title'
./scripts/eval.js 'document.querySelectorAll("a").length'
./scripts/eval.js 'document.querySelector("button")?.click(); "clicked"'
./scripts/eval.js 'await Promise.resolve(document.title)'
./scripts/eval.js 'JSON.stringify(Array.from(document.querySelectorAll("a")).map(a => ({ text: a.textContent.trim(), href: a.href })).filter(link => !link.href.startsWith("https://")))'Execute JavaScript in the active tab. Input can be an expression or statement list; the console-style completion value is printed and promises/top-level `await` are awaited. Be careful with string escaping, best to use single quotes.
./scripts/screenshot.js ./scripts/screenshot.js --full-page ./scripts/screenshot.js --device iphone-14 ./scripts/screenshot.js --device pixel-7 --full-page
Takes a screenshot and returns a temp file path.
./scripts/pick.js "Click the submit button"
Interactive element picker. Click to select, Cmd/Ctrl+Click for multi-select, Enter to finish. This requires headed Chrome; launch `start.js` without `--headless`.
./scripts/dismiss-cookies.js # Accept cookies ./scripts/dismiss-cookies.js --reject # Reject cookies (where possible)
Automatically dismisses EU cookie consent dialogs.
Run after navigating to a page:
./scripts/nav.js https://example.com && ./scripts/dismiss-cookies.js
./scripts/start.js --headless ./scripts/nav.js https://example.com ./scripts/emulate.js iphone-14 ./scripts/nav.js https://example.com # reload with mobile UA ./scripts/dismiss-cookies.js ./scripts/screenshot.js --full-page
Automatically started by `start.js` and writes JSONL logs to:
~/.cache/agent-web/logs/YYYY-MM-DD/<targetId>.jsonl
Manually start:
./scripts/watch.js
Tail latest log:
./scripts/logs-tail.js # dump current log and exit ./scripts/logs-tail.js --follow # keep following
Summarize network responses:
./scripts/net-summary.js
Armin's personal Pi Coding Agent package: reusable skills, extensions, prompt commands, themes, and a few supporting utilities that I use across projects. The package is published to npm as mitsupi.
Repo: mitsuhiko/agent-stuff
Austrian public transport (VOR AnachB) for all of Austria. Query real-time departures, search…
Search, read, and extract attachments from Apple Mail's local storage. Query emails by…
Transcribe local audio/video and Apple Voice Memos quickly with cached MLX Whisper models,…
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract…
Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for…