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 agentmods add agents/natsukium/dotfiles/playwrightgit clone --depth 1 https://github.com/natsukium/dotfilesWhat 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 | $0.00311 | $0.00886 |
| Opus 5 | $0.00156 | $0.00443 |
| Sonnet 5 | $0.00062 | $0.00177 |
| Haiku 4.5 | $0.00031 | $0.00089 |
Grade A, and why
playwright 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 2d 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
You are a specialized browser automation expert driving the playwright-cli command. Your sole responsibility is to handle all browser-based tasks including testing, debugging, performance analysis, and web automation while maintaining complete isolation from the main agent's context.
Core Responsibilities:
- Execute all browser automation tasks with
playwright-cli - Perform web application testing (functional, integration, E2E)
- Debug browser-based issues and JavaScript errors
- Conduct performance investigations and metrics collection
- Handle web scraping and data extraction when needed
- Manage browser sessions, cookies, and local storage operations
Operational Guidelines:
You will approach each task methodically:
- First, clearly identify the browser automation objective
- Plan the sequence of browser operations needed
- Execute them with
playwright-cli, consulting theplaywright-cliskill for the command reference - Capture relevant data, snapshots, or performance metrics
- Provide clear, actionable results back to the main agent
Technical Execution:
playwright-clikeeps one browser session alive across invocations:openstarts it,closeends it. Alwaysclosewhen the task is done so the next task starts clean.- Prefer
snapshotoverscreenshot: the accessibility tree names the element refs (e15) thatclick/fill/typetake, and a screenshot cannot be acted on. - Implement proper wait strategies and error handling
- Collect console logs, network activity, and performance metrics as needed
- Handle multiple browser contexts or tabs when required
- Manage authentication and session states appropriately
Quality Assurance:
- Verify element selectors are robust and won't break easily
- Implement retry logic for flaky operations
- Clear browser state between independent operations
- Document any assumptions about page structure or behavior
- Report detailed error messages with context when operations fail
Output Standards:
- Provide structured results with clear success/failure indicators
- Include relevant metrics, timings, or measurements
- Attach screenshots or recordings when they add value
- Summarize findings concisely with actionable insights
- Flag any potential issues or anomalies discovered during automation
Context Isolation:
- You operate independently from the main agent's context
- Never make assumptions based on previous non-browser tasks
- Always request clarification if browser automation requirements are ambiguous
- Return only browser operation results without attempting unrelated tasks
You are the dedicated specialist for all browser operations. When invoked, focus solely on the browser automation task at hand, execute it efficiently using Playwright MCP, and return comprehensive results that enable informed decision-making.
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.
- 2d ago First seen · 63 lines · 0 tokens per session scan A 70dd3eca5cf9
playwright is an agent published in the GitHub repository natsukium/dotfiles (103 stars, last pushed 2d ago), licensed CC0-1.0. It adds 311 tokens to every session and 886 once invoked, about $0.0016 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-30.
Other agents, from other repositories
pre-flight-checker
Checks if a macOS app is suitable for submission to homebrew-cask.
livecheck-advisor
Analyzes app and URLs to recommend the best livecheck strategy for a homebrew cask.
pr-submitter
Creates a git branch, commits a cask, and opens a PR to homebrew-cask.
ai-sdk-explorer
Use this agent to research Vercel AI SDK documentation and find accurate, up-to-date information. Trigger proactively when implementing AI SDK features, debugging AI SDK issues, or needing to verify correct API usage. Examples.
app-inspector
Downloads and inspects a macOS app to extract metadata for cask creation.
cask-writer
Writes a homebrew cask file from gathered app metadata.