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.
git clone --depth 1 https://github.com/JuanMarchetto/agent-skillsWrote 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/plugins/juanmarchetto/agent-skills/playwright-recording)<a href="https://agentmods.dev/plugins/juanmarchetto/agent-skills/playwright-recording"><img src="https://agentmods.dev/badge/plugins/juanmarchetto/agent-skills/playwright-recording.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
playwright-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 4d 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.
What it actually says
{
"name": "playwright-recording",
"description": "Record browser interactions as video using Playwright for demos, walkthroughs, and UI flows",
"version": "1.0.0",
"author": { "name": "Juan Marchetto" },
"homepage": "https://github.com/JuanMarchetto/playwright-recording-skill",
"repository": "https://github.com/JuanMarchetto/playwright-recording-skill",
"license": "MIT"
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 59 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 4d ago First seen · 10 lines scan A 466664831d35
playwright-recording is a plugin published in the GitHub repository JuanMarchetto/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-09-03.
Other plugins, from other repositories
cli-anything
Reference guide for CLI-Anything: auto-generate production-ready agent-controllable CLI harnesses for any GUI app via 7-phase pipeline. Covers all validated commands, per-app examples (GIMP, Blender, LibreOffice, Inkscape), testing, and HARNESS.md methodology.
kokoro-tts
Local Kokoro TTS engine: MLX-Audio install, HTTP server, voice synthesis, health checks, diagnostics (Apple Silicon).
media-tools
YouTube audio download, iOS device media transfer, and HEIC-to-JPEG photo-share workflows.
devharness
Run and debug a live app from inside Claude Code: breakpoints and variable inspection in Chrome and Node.js, managed dev servers, and replayable call history so setup is never re-driven by hand.
mochi
A browser companion for AI assistants. Bundled MCP tools for Chrome automation, persistent project memory (Continuum chain), and an in-page hint modal — pair with the Mochi Chrome extension.
LUXOR Specialized Tools
Specialized developer tools including Playwright, Linear, asyncio patterns, unix-goto, and Pydantic.