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 ugarchance/record-and-replay-skill --skill record-and-replay-skillgit clone --depth 1 https://github.com/ugarchance/record-and-replay-skillWrote 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/ugarchance/record-and-replay-skill/record-and-replay-skill)<a href="https://agentmods.dev/skills/ugarchance/record-and-replay-skill/record-and-replay-skill"><img src="https://agentmods.dev/badge/skills/ugarchance/record-and-replay-skill/record-and-replay-skill/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/ugarchance/record-and-replay-skill/record-and-replay-skill"><img src="https://agentmods.dev/badge/skills/ugarchance/record-and-replay-skill/record-and-replay-skill.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.00106 | $0.03589 |
| Opus 5 | $0.00053 | $0.01795 |
| Sonnet 5 | $0.00021 | $0.00718 |
| Haiku 4.5 | $0.00011 | $0.00359 |
Grade A, and why
record-and-replay 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 12d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Record & Replay (browser + desktop)
Record & Replay lets an agent learn a user-demonstrated workflow and turn it into a reusable skill. Two modes:
- Browser mode (default, richest evidence): a headed Playwright browser (system Google Chrome if available) records every user action into
events.jsonlwith multiple selector candidates, plus Playwright trace chunks (trace-NNN.zip). Works on macOS, Windows and Linux. - Desktop mode (native apps): a lightweight single-process recorder (pynput) captures global mouse/keyboard events, active-window changes and click-moment screenshots into
desktop-events.jsonl+screens/— Codex-parity (Codex records an event/context stream too, not video), ~1-3% CPU. Works on macOS, Windows and Linux (X11). See "Desktop recording" below.
Pick browser mode whenever the workflow is browser-only — its semantic selectors produce far better skills than desktop coordinates.
Setup (once)
cd ~/.agents/skills/record-and-replay
node setup.mjs # npm install + (Chromium only if Chrome is missing) + self-tests
node install.mjs # link into agent skill dirs (symlink on macOS/Linux, junction on Windows)
Installs the playwright npm package. Browsers are NOT downloaded when Google Chrome is installed (the recorder uses channel: 'chrome'); otherwise the script downloads Chromium. Both scripts are cross-platform (Node).
Recording Workflow
-
Start the recorder detached in the background only when the user is ready to begin. Always pass
--name <slug>so the output directory is known up front:cd ~/.agents/skills/record-and-replay # macOS / Linux: nohup node scripts/recorder.mjs --minutes 30 --name <slug> [--url <startUrl>] \ > ~/.agents/recordings/recorder.log 2>&1 & # Windows (PowerShell): Start-Process node -WindowStyle Hidden -ArgumentList "scripts/recorder.mjs","--minutes","30","--name","<slug>"Agents with a native background-run facility (e.g. Claude Code's Bash
run_in_background) may use it instead. Outputs go to~/.agents/recordings/<slug>/.
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.
- 12d ago First seen · 123 lines · 106 tokens per session scan A bb288f8965c8
record-and-replay is a skill published in the GitHub repository ugarchance/record-and-replay-skill (36 stars, last pushed 1mo ago), licensed MIT. It adds 106 tokens to every session and 3,589 once invoked, about $0.0005 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
playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
playwright-component-testing
Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue.
agent-browser
Drive a real browser to inspect or interact with a web page or app — navigate, take screenshots, read console and network, fill simple forms — for verification tasks, not unattended automation.
dev-browser
Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, log into sites, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot"…
playwright-recording
Record browser interactions as video using Playwright. Use for capturing demo videos, app walkthroughs, and UI flows for Remotion videos. Triggers include recording a demo, capturing browser video, screen recording a website, or creating walkthrough footage.
moli-webfetch
Fetch, inspect, crawl, and capture live, JavaScript-rendered websites with Moli. Use when Codex needs current web content, web research, fact lookup, link following, a bounded crawl, client-rendered or response-gated content, network diagnostics, or a standalone HTML, Markdown, JSON, semantic-tree, viewport or…