claude-tap is a local proxy and trace viewer for AI coding agents, recording and displaying their API requests, prompts, tool calls, responses, context, and token usage. It helps developers inspect and compare agent runs from tools such as Claude Code, Codex CLI, Gemini CLI, Cursor CLI, and others, while the catalogue skills and instruction support work with the project.
Borrowing it
Nothing to install: this file belongs to liaohch3/claude-tap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/liaohch3/claude-tap/main/.agents/skills/playwright-screen-recording/SKILL.mdgit clone --depth 1 https://github.com/liaohch3/claude-tapWrote 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/liaohch3/claude-tap/playwright-screen-recording)<a href="https://agentmods.dev/skills/liaohch3/claude-tap/playwright-screen-recording"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/playwright-screen-recording/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/liaohch3/claude-tap/playwright-screen-recording"><img src="https://agentmods.dev/badge/skills/liaohch3/claude-tap/playwright-screen-recording.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.00645 |
| Opus 5.5 | $0.00008 | $0.00258 |
| Sonnet 5.5 | $0.00004 | $0.00129 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
playwright-screen-recording 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 1mo 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Screen Recording for Test Verification
Use Playwright's video recording to capture headless browser operations as .webm videos for PR review or bug fix verification.
Core Usage
from playwright.sync_api import sync_playwright
import tempfile
from pathlib import Path
video_dir = Path(tempfile.mkdtemp())
with sync_playwright() as pw:
browser = pw.chromium.launch(headless=True)
context = browser.new_context(
viewport={"width": 1400, "height": 900},
record_video_dir=str(video_dir),
record_video_size={"width": 1400, "height": 900},
)
page = context.new_page()
page.goto(f"file:///path/to/test.html")
# ... perform test actions, add pauses for readability ...
page.wait_for_timeout(800) # pause so viewers can see the current state
page.close()
context.close() # video is finalized after context.close()
browser.close()
# Retrieve the recorded video
videos = list(video_dir.glob("*.webm"))
if videos:
videos[0].rename("demo.webm")
Use Cases
- Bug fix verification: record before/after comparisons showing button state changes, UI behavior differences
- PR Review: attach .webm video so reviewers can visually understand the change
- Regression test evidence: record critical interaction paths as visual proof of passing tests
Recording Tips
Add pauses between actions
page.click(".some-button")
page.wait_for_timeout(800) # let viewers see the click effect
page.keyboard.press("ArrowRight")
page.wait_for_timeout(600) # let viewers see the navigation result
Combine assertions with terminal logging
state = get_nav_state(page)
print(f"[1] Title: {state['title']}")
print(f" prev disabled: {state['prevDisabled']} (expected: True)")
assert state["prevDisabled"] is True
print(" PASS")
Terminal output paired with the recorded video provides dual verification.
Prefer real data
Use existing real trace data from the project rather than synthetic data for more convincing demos:
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.
- 1mo ago First seen · 93 lines · 20 tokens per session scan A 7d38a7a31fa7
playwright-screen-recording is a skill published in the GitHub repository liaohch3/claude-tap (3,312 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 645 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
test-e2e
Generates end-to-end tests for a user flow using Playwright or Cypress.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
browser-use
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers hosted cloud browsers for AI agents: the browser-use Python library (Browser(usecloud=True)), Playwright, Puppeteer or any CDP client.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.