agentmods.dev

screencast

screencast is a skill for Claude Code from mthines/agent-skills. It costs 103 tokens per session (1,315 once invoked), scanned A, original, MIT.

A browser-video recording workflow that captures scripted interactions or Playwright test runs, adds visible step captions and click markers, and outputs review files.

In plain words
What is it for?
Use it to record product interactions, demonstrate workflows, or review browser test runs as MP4 videos with timing files and contact sheets.
Why use it?
It turns raw browser recordings into shorter videos with timing information and step-by-step visual evidence.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Part of the mthines-agent-skills plugin — 49 skills, 3 agents shipped together

not rated 20repo +3 changed today A scan 103 tokens original MIT

Good fit Use it to record product interactions, demonstrate workflows, or review browser test runs as MP4 videos with timing files and contact sheets.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mthines/agent-skills/screencast
View source ↗ mthines/agent-skills
Install

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.

Any agent
npx skills add mthines/agent-skills --skill screencast
Clone the repo
git clone --depth 1 https://github.com/mthines/agent-skills

Made for: Claude Code.

Or install mthines-agent-skills, the plugin that ships this one along with the rest of its 49 skills, 3 agents.

Wrote 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.

agentmods badge for screencast

README.md
[![agentmods](https://agentmods.dev/badge/skills/mthines/agent-skills/screencast/github.svg)](https://agentmods.dev/skills/mthines/agent-skills/screencast)
Your own site
<a href="https://agentmods.dev/skills/mthines/agent-skills/screencast"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/screencast/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.

agentmods 80×15 button for screencast

Your own site · 80×15
<a href="https://agentmods.dev/skills/mthines/agent-skills/screencast"><img src="https://agentmods.dev/badge/skills/mthines/agent-skills/screencast.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 103 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,315 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00103 $0.01315
Opus 5.5 $0.00041 $0.00526
Sonnet 5.5 $0.00021 $0.00263
Haiku 4.5 $0.00010 $0.00131

Measured today against content hash a79b56646ed1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

screencast 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 today.

The scan reads SKILL.md. This mod also ships 4 executable files (scripts/capture.mjs, scripts/finish.mjs, scripts/overlay.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/analysis/screencast/SKILL.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

screencast

Scripts do the work; this file lists only what differs from a plain Playwright recordVideo + ffmpeg job.

Script Use
scripts/record.mjs <recording.json> Scripted scenes (caption + click/hover/type/press/scroll/wait steps); schema in the file header. Run from a directory where playwright resolves
scripts/overlay.js A test runner's own recording: context.addInitScript({ path }), then window.__rec.step(label) per step
scripts/finish.mjs <raw.webm>... --out <id>.mp4 Any raw video(s) + sibling <stem>.timings.json → the outputs below. --crop x,y,w,h, --max-width 768 for video-analyser, --no-trim
scripts/capture.mjs launch [--port 9222] | disconnect | start --url <part> | step "<label>" | stop --out <id>.mp4 A Chrome tab another tool drives (claude-in-chrome): streams its frames over the DevTools protocol through a relay that keeps one connection to Chrome, then runs finish.mjs on stop. disconnect closes that connection. launch opens a separate Chrome with a DevTools port, for when remote debugging at chrome://inspect is off. Usage and exit codes in the file header 
node "${CLAUDE_SKILL_DIR}/scripts/finish.mjs" spec-1-1.webm spec-1-2.webm --out .agent/feat-x/.aw-tester/recordings/spec-1.mp4

Outputs (the contract other skills read)

<id>.mp4, <id>.timings.json (steps: [{ label, start, end, result }] in output seconds), and <id>.sheet.png (one frame per step), side by side. Standalone runs write to .agent/{branch}/recordings/; a caller such as aw-tester keeps its own directory.

Deviations from the default

  1. Read <id>.sheet.png before any upload or claim. You cannot watch a video; the sheet is how you check it shows what you say it shows.
  2. Record at 1x. Playwright video ignores deviceScaleFactor: a 2x page lands in a corner of the frame. Upscale in ffmpeg if needed.
  3. Hide the overlay in screenshots: page.screenshot({ style: '#__screencast{display:none!important}' }), so evidence images show only the app.
  4. A runner writes timings as it goes: { label, start, end, result } per step, seconds from newPage(); several launches → pass every segment to finish.mjs in order, and it joins them and offsets their timings.
  5. A failed recording is a notes line, never a failed check.
  6. Chrome driver (claude-in-chrome): no recordVideo, so record with capture.mjs, never gif_creator: a GIF gets one frame per tool call and is ~20× larger than the mp4. It needs Chrome's remote debugging on once (chrome://inspect/#remote-debugging), and the user clicks Allow once per Chrome session: the first start prints connecting to Chrome and waits, and later ones reuse the relay's connection. --wait 600 when you start it before asking. Chrome paints only while the page changes and its window is visible, so the video starts at the first frame after start, and stop exits 6 if none came. Run overlay.js's source with javascript_tool after every navigation and call __rec.step(label) with each capture.mjs step, or the video has no captions. Exit 6 (no debugging, no matching tab, no frames) → fall back to gif_creator, convert the GIF (ffmpeg -i x.gif -movflags +faststart -vf "scale=1280:-2,format=yuv420p" -c:v libx264 -crf 28 -an x.mp4), and add a notes line.
  7. Narration is opt-in (--narrate): each step's say line, spoken with macOS say or SCREENCAST_TTS="<cmd with {text} and {out}>". Never by default — reviewers watch muted.

Read the full file on GitHub · 53 lines

Files

What ships with it

4 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.

Changes

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.

  1. today Changed · +5 lines · +17 tokens per session a79b56646ed1
  2. yesterday First seen · 48 lines · 86 tokens per session scan A d1efd26a6e85

Subscribe to this mod's changes

screencast is a skill published in the GitHub repository mthines/agent-skills (20 stars, last pushed today), licensed MIT. It adds 103 tokens to every session and 1,315 once invoked, about $0.0004 per session on Opus 5.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-10-23.

Browser automationClaude CodeE2E testingTestingaiclaudeskillsskills-sh
Related

Other skills, from other repositories

browser-testing-with-devtools

Use Chrome DevTools MCP to inspect, debug, and verify anything that runs in a browser — DOM structure, console errors, network requests, performance traces, and accessibility. Use when building or fixing browser UI, diagnosing a runtime bug that isn't visible from source code alone, or verifying a fix actually works…

shennawardana23/skillme · 80 tokens

browser-testing-with-devtools

Tests in real browsers via Chrome DevTools MCP. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data. Requires the chrome-devtools MCP server to be…

addyosmani/agent-skills · 68 tokens

actionbook-web-test

Run browser-based web tests against websites using Actionbook CLI. Activate when the user wants to test a website workflow, run smoke tests, verify a user flow, check if a web application works, run regression tests, or validate browser-based interactions. Supports test definition, execution, assertion, reporting, and…

actionbook/actionbook · 71 tokens

web-test

A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.

Nikolay-Shirokov/cc-1c-skills · 44 tokens

playwright-visual-testing

Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…

managedcode/dotnet-skills · 101 tokens

appbuilder-e2e-testing

Use this skill whenever the user wants browser-based end-to-end tests for an Adobe App Builder application. Covers Playwright E2E testing for ExC Shell SPAs, AEM extension UIs, and full-stack flows. Use when the user mentions: "E2E test", "end-to-end test", "Playwright", "browser test", "test my SPA in the browser"…

adobe/skills · 144 tokens