Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add joaquimscosta/arkhe-claude-plugins/plugin install devtoolsWrote 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/joaquimscosta/arkhe-claude-plugins/browser-companion)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/browser-companion"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/browser-companion/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/joaquimscosta/arkhe-claude-plugins/browser-companion"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/browser-companion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00138 | $0.01252 |
| Opus 5 | $0.00069 | $0.00626 |
| Sonnet 5 | $0.00028 | $0.00250 |
| Haiku 4.5 | $0.00014 | $0.00125 |
Grade A, and why
browser-companion 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 11d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Companion
A zero-dependency Node.js HTTP + WebSocket server that turns a directory of HTML fragments into a live-reloading preview, with browser→agent click event capture.
The skill ships a public CLI arkhe-preview placed in plugins/devtools/bin/. Any plugin's skill can invoke it as a bare bash command — no need to know the devtools install path.
Quick Start
# Start a server scoped to the current project
arkhe-preview start --project-dir "$(pwd)"
# Output (one JSON line on stdout):
# {"type":"server-started","port":54123,"url":"http://localhost:54123",
# "screen_dir":".../<id>/content","state_dir":".../<id>/state",
# "session_dir":".../<id>","pid":12345}
# Tell the user to open the URL. Then write HTML to screen_dir:
echo '<h2>Hello</h2><button data-event="ok">OK</button>' > "$SCREEN/content.html"
# Browser auto-reloads. User clicks. Read events:
tail -f "$STATE/events.jsonl"
# When done:
arkhe-preview stop "$SESSION_DIR"
When to Use This
- Design / mockup loops — write HTML to
screen_dir, browser shows it - Multi-select / variant selection — give the user clickable options, read events.jsonl to learn what they picked
- Iteration on generated UI — overwrite fragment → instant reload
- Cross-plugin — any plugin's skill can call
arkhe-previewdirectly; it lives in devtools but its CLI is on PATH whenever devtools is enabled
Core Commands
arkhe-preview start [options] # Print {url, screen_dir, state_dir, session_dir, pid} JSON
arkhe-preview stop <session-dir> # Graceful SIGTERM, falls back to SIGKILL
arkhe-preview status <session-dir> # {running, pid, url} JSON (always exits 0)
arkhe-preview --help # Full option reference (USAGE.txt)
Common start options:
--project-dir <path>— store under<path>/.claude/preview/<id>/(default:/tmp/arkhe-preview-<id>/)--frame-template <path>— override default HTML frame--helper <path>— override default browser-side helper JS--port <N>— pin a specific port--owner-pid 0— disable the watchdog (use idle timeout only)
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- EXAMPLES.md 6.9 KB
- examples/brainstorm/frame-template.html 5.3 KB
- examples/brainstorm/helper.js 4.1 KB runs code
- examples/brainstorm/README.md 2.2 KB
- examples/gallery/frame-template.html 1.3 KB
- examples/gallery/helper.js 2.0 KB runs code
- examples/gallery/README.md 2.7 KB
- scripts/frame-template.html 2.6 KB
- scripts/helper.js 2.5 KB runs code
- scripts/server.cjs 13 KB runs code
- scripts/start-server.sh 6.0 KB runs code
- scripts/status-server.sh 1.0 KB runs code
- scripts/stop-server.sh 1.9 KB runs code
- TROUBLESHOOTING.md 7.6 KB
- USAGE.txt 3.0 KB
- WORKFLOW.md 9.7 KB
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.
- 11d ago First seen · 113 lines · 138 tokens per session scan A cb963059e156
browser-companion is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed 28d ago), licensed MIT. It adds 138 tokens to every session and 1,252 once invoked, about $0.0007 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
demo-video
Orchestrates building a narrated demo video of a project — reads the codebase, writes a storyboard, prepares deterministic app state, drives the UI with Playwright to record clips (web and Electron), generates ElevenLabs voiceover, reconciles measured durations into a timeline, and renders the final cut with Remotion.…
demo-capture
Records demo video clips by driving a running app — one clip per storyboard section, with human-feeling pointer motion, dwell timing, and per-character typing. Covers the Playwright MCP video tools for web apps and a generated Playwright Electron script (plus a macOS screen-capture fallback) for desktop apps. Use when…
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
web-access
A method for handling difficult web tasks across search, page fetching, and a real browser. It covers sites that need login sessions, dynamic pages, anti-bot handling, or exploration before their structure is understood.
responsiveness-check
Test website responsiveness across viewport widths using browser automation. Resizes a single session through breakpoints, screenshots each width, and detects layout transitions (column changes, nav switches, overflow). Produces comparison reports showing exactly where layouts break. Trigger with 'responsiveness…