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 skills/openknots/okcode/playwrightnpx skills add OpenKnots/okcode --skill playwrightgit clone --depth 1 https://github.com/OpenKnots/okcodeWhat 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.00011 | $0.00417 |
| Opus 5 | $0.00005 | $0.00209 |
| Sonnet 5 | $0.00002 | $0.00083 |
| Haiku 4.5 | $0.00001 | $0.00042 |
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 yesterday.
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
Playwright Skill
When to use this skill
- Use when the task needs browser automation, UI verification, end-to-end testing, or scripted web interactions.
- Use when the user needs reproducible validation of browser behavior rather than manual spot-checking.
- Use when screenshots, DOM assertions, navigation flows, or form automation are part of the task.
- Use when the user wants a reliable browser-based regression check from the terminal.
What this skill does
- Designs Playwright workflows that are deterministic, inspectable, and resilient to minor UI changes.
- Prefers stable selectors and event-driven waits over brittle timing assumptions.
- Captures actionable failure context such as URLs, selectors, screenshots, and expectation mismatches.
- Keeps test intent focused on behavior, not incidental implementation details.
Implementation
- Clarify whether the goal is one-off browser automation, a reusable test, or a debugging workflow.
- Prefer semantic selectors and stable locators over deep CSS selectors tied to styling structure.
- Use assertions that reflect user-observable behavior rather than implementation accidents.
- Prefer waits based on navigation, visible UI state, or network/DOM readiness rather than arbitrary sleep intervals.
- If the task is exploratory, keep scripts short and focused on reproducing the target behavior.
- If the task is test authoring, structure steps and assertions so failures are easy to diagnose.
- Capture enough context on failure for a human to reproduce and fix the issue quickly.
Best practices
- Avoid timing-based waits unless no stronger signal exists.
- Keep selectors robust and understandable.
- Prefer behavior-level assertions over snapshotting everything.
- Include screenshots or other evidence when reporting a browser failure.
- Keep scripts and tests maintainable; do not overfit to current DOM noise.
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.
- yesterday First seen · 50 lines · 11 tokens per session scan A 6e0e017d388a
playwright is a skill published in the GitHub repository OpenKnots/okcode (24 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 417 once invoked, about $0.0001 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 skills, from other repositories
general-video
Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
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…
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.
mintlify-preview
Run the public Mintlify product docs site locally for live preview. Use when previewing or iterating on docs under docs/ (.mdx/.md pages, docs.json nav), or when the user says "start the docs", "run mintlify", "preview the docs site".