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.
npx skills add neonwatty/playwright-profiles --skill capture-authgit 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/skills/neonwatty/playwright-profiles/capture-auth)<a href="https://agentmods.dev/skills/neonwatty/playwright-profiles/capture-auth"><img src="https://agentmods.dev/badge/skills/neonwatty/playwright-profiles/capture-auth.svg" alt="Measured on agentmods" height="20"></a>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.00133 | $0.02449 |
| Opus 5 | $0.00067 | $0.01224 |
| Sonnet 5 | $0.00027 | $0.00490 |
| Haiku 4.5 | $0.00013 | $0.00245 |
Grade A, and why
capture-auth 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 6d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Capture Web App Authentication
Save reusable authenticated browser sessions for custom web apps (the user's own projects, client apps, staging environments, etc.) using the persistent Chrome profile at ~/.playwright-cli/.
How This Differs from auth-browse
- auth-browse: Preconfigured external services (Cloudflare, Sentry, Vercel, etc.) with known
waitForpatterns - capture-auth: The user's own apps — custom URLs where the post-login URL needs to be discovered
Both use the same ~/.playwright-cli/sign-in.mjs script and shared Chrome profile.
Workflow
Step 1: Gather app details
Ask the user for:
- A short name for the app (e.g.,
deckchecker,seatify-staging,client-portal). Used as the identifier for future sign-ins. - The login URL (e.g.,
https://deckchecker.app/login,https://staging.seatify.app/login). - The post-login URL pattern (optional). This is a URL substring that appears after successful sign-in — used for auto-detect. Examples:
/dashboard— most common/home/events- The app's domain alone if login redirects to a different domain
If the user does not know the post-login URL, suggest common patterns or tell them to skip it (the script will use manual Enter instead).
Step 2: Register the site
Run via Bash:
node ~/.playwright-cli/sign-in.mjs add <name> <login-url> <wait-for-pattern>
Example:
node ~/.playwright-cli/sign-in.mjs add deckchecker https://deckchecker.app/login /dashboard
If no waitFor was provided, omit the third argument — the script defaults to the hostname.
Step 3: Sign in
Tell the user to run the sign-in command in a separate terminal:
node ~/.playwright-cli/sign-in.mjs login <name>
The script defaults to Playwright's built-in Chromium, which works while Chrome is open. Custom apps rarely have bot detection, so this is almost always fine. If the user's app uses Google OAuth for login and it gets blocked, retry with --tier chrome (Chrome must be closed first):
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.
- 6d ago First seen · 239 lines · 133 tokens per session scan A 6d8eed207381
capture-auth is a skill published in the GitHub repository neonwatty/playwright-profiles (4 stars, last pushed 4mo ago), licensed MIT. It adds 133 tokens to every session and 2,449 once invoked, about $0.0007 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.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
azure-messaging-webpubsub-java
Build real-time web applications with Azure Web PubSub SDK for Java. Use when implementing WebSocket-based messaging, live updates, chat applications, or server-to-client push notifications.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…