Cm Browse

Name: Cm Browse
Author: tody-agent

ASecurity

Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright.

52 stars
0 votes
0 copies
1 view
Added May 29, 2026

ai-agentsbashnodetestingapi

Works with

Security analysis

A100/100

Scanned May 29, 2026

npx -y skills add tody-agent/codymaster --skill cm-browse --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cm Browse?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/tody-agent-cm-browse/badge)](https://www.skillsdirectory.com/skills/tody-agent-cm-browse)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: cm-browse
description: "Use when you need visual QA, screenshots, or post-deploy smoke testing through a real browser with Playwright."
---
# cm-browse — local Playwright daemon

> **Full runbook:** [docs/browse-daemon.md](../../docs/browse-daemon.md) (install Chromium, token, troubleshooting).

## When to use

- Visual QA, screenshots, post-deploy smoke through a **real browser** (not only Stitch/Pencil).
- Before claiming “UI works”, drive `cm browse` + `cm qa-visual`.

## CLI

```bash
export CM_BROWSE_TOKEN="$(openssl rand -hex 24)"
cm browse start --port 17395 --token "$CM_BROWSE_TOKEN"
```

## HTTP API (Bearer token)

- `POST /session/start` body `{ "headless": true }`
- `POST /navigate` `{ "url": "https://…" }`
- `POST /refs/refresh` — assigns `data-cm-ref` to interactive nodes; use `@e1` style refs.
- `POST /click` `{ "ref": "e1" }`
- `POST /fill` `{ "ref": "e2", "value": "text" }`
- `GET /screenshot` — PNG
- `GET /console` / `GET /network` — ring buffers

## Integrations

- `cm qa-visual --url …` calls the daemon locally.
- Pair with `cm-canary` / `cm-safe-deploy` for ship verification.