agentmods.dev

ui-recorder

ui-recorder is a skill for Claude Code from procoders/claude-ui-recorder. It costs 80 tokens per session (1,373 once invoked), scanned A, original, MIT.

A workflow for recording a website as a narrated 16:9 MP4 demo. It plans browser actions, records the interface, creates narration, edits the result, and renders the video.

In plain words
What is it for?
Use it for screen demos, website walkthroughs, marketing clips, and narrated recordings of web interfaces.
Why use it?
It helps turn a website walkthrough into a repeatable video while checking that the planned actions match the real page before recording.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the ui-recorder plugin — 1 skill, 2 agents, 1 hook shipped together

not rated 2repo 4mo ago A scan 80 tokens original MIT

Good fit Use it for screen demos, website walkthroughs, marketing clips, and narrated recordings of web interfaces.

Compare 6 skills from other repositories ↓
View source ↗ procoders/claude-ui-recorder
Install

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.

Claude Code
/plugin marketplace add procoders/claude-ui-recorder
Claude Code
/plugin install ui-recorder

Made for: Claude Code.

Or install ui-recorder, the plugin that ships this one along with the rest of its 1 skill, 2 agents, 1 hook.

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 ui-recorder

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/procoders/claude-ui-recorder/ui-recorder"><img src="https://agentmods.dev/badge/skills/procoders/claude-ui-recorder/ui-recorder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,373 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.00080 $0.01373
Opus 5 $0.00040 $0.00687
Sonnet 5 $0.00016 $0.00275
Haiku 4.5 $0.00008 $0.00137

Measured 8d ago against content hash 51ec485333d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

ui-recorder 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 8d 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.

skills/ui-recorder/SKILL.md · 82 lines

How it starts

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

ui-recorder Skill

Orchestrates the 5-stage pipeline: plan → record → narrate → edit → render.

Workflow

Stage 0 — Plan-Build (verifies selectors against real DOM)

  1. Slugify the user's description → workspace slug.
  2. Run: node "${CLAUDE_PLUGIN_ROOT}/scripts/plan-build.mjs" <slug> -- <user-prompt>
  3. Read stdout:
    • BYPASS → user already placed browse-plan.json (e.g. from test-fixtures/). A synthetic plan-report.json was written with source: "user-provided" for all actions. Skip to Stage 1.
    • NEEDS_AGENT → workspace is empty. Dispatch the plan-builder agent (Task tool, subagent_type plan-builder). Pass it the workspace path, user prompt, viewport, and playbackRate. The agent writes browse-plan.json, plan-report.json, and narration.txt into the workspace.
  4. On agent failure (errors in stderr): surface the code + hint. If it reports PLAN_CHROMIUM_MISSING and no browser MCP was available, offer the user: (a) run setup.sh to install chromium, (b) proceed with the agent's partial plan, marking unverified actions as blind manually, (c) edit plan manually.

Stage 1 — Review (Gate 1)

  1. Read workspace/{slug}/browse-plan.json and plan-report.json. Present to the user:
    • Summary: N actions across M URLs, estimated output ~Xs at the configured playbackRate.
    • Per-action line: #N <action> <label> — selector: <sel> [confidence: <level>, source: <tier>] + short rationale.
    • If any action has source: "blind", flag with a warning icon and show the warning field.
  2. Gate 1: "Proceed? (yes / edit selector N / drop action N / regenerate)". Wait for explicit approval.
  3. On "edit" — update browse-plan.json and the matching action in plan-report.json (change source to "user-provided"), then re-prompt.
  4. On "regenerate" — ask the user for a refined prompt, then rerun Stage 0 from step 2.

Stage 2 — Record

  1. Invoke node "${CLAUDE_PLUGIN_ROOT}/scripts/record.mjs" <plan.json> <slug>.
  2. On failure, surface the code + hint from UIRecorderError. Suggest the fix verbatim.
  3. On success, report: recording.mp4 path, moments.json summary (N actions captured, total duration).

Read the full file on GitHub · 82 lines

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. 8d ago First seen · 82 lines · 80 tokens per session scan A 51ec485333d0

Subscribe to this mod's changes

ui-recorder is a skill published in the GitHub repository procoders/claude-ui-recorder (2 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 1,373 once invoked, about $0.0004 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-31.

Browser automationCreative and media
Related

Other skills, from other repositories

feature-demo-recording

Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…

kirodotdev/KiroCrew · 90 tokens

browser-video-recording

Create polished 60 fps 4:3 4K browser screen-recording style videos from Codex in-app browser captures, with browser-only crop, natural macOS cursor styling, deliberate click choreography, zoom-follow framing, ffprobe/thumbnail verification, and optional native recording compatibility checks. Use when the user asks to…

MengTo/Skills · 114 tokens

html-to-video-pipeline

Reliable HTML-to-MP4 rendering via headless browser recording (Playwright/Puppeteer) + ffmpeg — the ordering, gotchas, and verification steps you MUST get right or the output silently rots. Trigger whenever the user is building or debugging any pipeline that turns an HTML/CSS/JS page (single-file, multi-composition…

XiaomiMiMo/MiMo-Code · 0 tokens

record-video

Record and upload a short browser interaction video artifact.

ColeMurray/background-agents · 12 tokens

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.

digitalsamba/claude-code-video-toolkit · 53 tokens

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.

calesthio/OpenMontage · 53 tokens