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.
/plugin marketplace add neonwatty/playwright-profilesnpx agentmods add plugins/neonwatty/playwright-profiles/marketplacegit clone --depth 1 https://github.com/neonwatty/playwright-profilesWrote 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/neonwatty/playwright-profiles/marketplace)<a href="https://agentmods.dev/plugins/neonwatty/playwright-profiles/marketplace"><img src="https://agentmods.dev/badge/plugins/neonwatty/playwright-profiles/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
neonwatty-playwright-profiles marketplace 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": "neonwatty-playwright-profiles",
"owner": { "name": "Jeremy Watt", "github": "neonwatty" },
"metadata": {
"description": "Auth-only Claude Code plugin for Playwright profiles and persistent authenticated browsing."
},
"plugins": [
{
"name": "playwright-profiles",
"source": { "source": "github", "repo": "neonwatty/playwright-profiles" },
"description": "Auth-only Claude Code plugin for Playwright profiles, persistent external-service auth, custom app auth capture, and bot-detection-aware browsing. Use neonwatty/qa-skills for the full QA workflow plugin.",
"version": "2.0.0",
"category": "browser",
"tags": [
"playwright",
"authentication",
"browser",
"profiles",
"multi-user",
"qa",
"bot-detection"
]
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
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 · 26 lines scan A d2523bde3e51
neonwatty-playwright-profiles marketplace is a plugin published in the GitHub repository neonwatty/playwright-profiles (4 stars, last pushed 4mo 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-08-31.
Other plugins, from other repositories
kernel-sdks
TypeScript and Python SDK skills for building browser automation with Kernel's Typescript and Python SDKs.
realbrowser
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions.
rad-chrome-extension
MV3 Chrome extension development standards (WXT, React, TypeScript) with two pure-stdlib Python validators that catch what LLM eyeballing misses. Skills cover architecture, MV3 security (CSP, remote code ban, content script isolation), permission minimization and CWS compliance, typed messaging, storage selection…
chrome-multi-instance-warn
An agent driving a browser tends to start a new one rather than use the one already open, and to size its work off the core count. This warns once per session when a tool payload is about to do either. Never blocks.
headless
Headless browser automation for site comparison, E2E testing, and anti-bot-aware web research.
claudeshot
Lightweight screenshot capture for Claude Code. PREFERRED over Playwright for web screenshots - uses headless Chrome directly without MCP overhead. Use /screenshot --web URL for quick page captures instead of Playwright browser tools.