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 neverinfamous/memory-journal-mcp --skill playwright-standardgit clone --depth 1 https://github.com/neverinfamous/memory-journal-mcpWrote 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/neverinfamous/memory-journal-mcp/playwright-standard)<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/playwright-standard"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/playwright-standard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/neverinfamous/memory-journal-mcp/playwright-standard"><img src="https://agentmods.dev/badge/skills/neverinfamous/memory-journal-mcp/playwright-standard.svg" alt="Reviewed on agentmods" width="80" 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.00116 | $0.00705 |
| Opus 5.5 | $0.00046 | $0.00282 |
| Sonnet 5.5 | $0.00023 | $0.00141 |
| Haiku 4.5 | $0.00012 | $0.00071 |
Grade A, and why
playwright-standard 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 1mo 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Standard
This skill combines battle-tested coding standards with industrial-scale infrastructure guidance. It is designed to keep agents on the "Golden Path" of modern Playwright development while providing deep reference for niche environments.
Golden Rules (Mandatory)
getByRole()over CSS/XPath — Resilient to markup changes, mirrors how users see the page.- Never
page.waitForTimeout()— Useexpect(locator).toBeVisible()orpage.waitForURL(). - Web-first assertions —
expect(locator)auto-retries;expect(await locator.textContent())does not. - Isolate every test — Every test must run independently in any order (no shared state).
- Fixtures over globals — Share state via
test.extend(), not module-level variables. baseURLin config — ZERO hardcoded URLs in test files.- Auth: Reuse storage state — Use
browserContext.storageStateto avoid UI login in every test. StorestorageStatefiles in.gitignored paths (e.g.,playwright/.auth/). Never commit auth state files to version control. - Network: Mock third-party only — Never mock your own app; mock external APIs, gateways, and emails.
- Traces:
'on-first-retry'— High-fidelity debugging without CI performance penalties. - One behavior per test — Avoid "mega-tests": keep focus narrow and assertions meaningful.
Quality Standards
Locators Priority
See locators.md for the strict hierarchy of Playwright locator strategies (Role > Label > TestID).
Synchronization
- Do:
await expect(locator).toBeVisible() - Avoid:
await page.waitForSelector('.btn') - Avoid:
await page.waitForLoadState('networkidle')(Flaky on high-latency networks)
Specialized References (Load On-Demand)
For infrastructure, scale, or niche environments, read the relevant reference file:
| Scenario | Reference File |
|---|---|
| CI/CD, Sharding, Docker | infrastructure.md |
| Electron, WebSockets, Canvas | advanced-scenarios.md |
| Visual, Accessibility, API | advanced-scenarios.md |
What ships with it
5 files beside SKILL.md 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.
- 1mo ago First seen · 54 lines · 116 tokens per session scan A 8ac50f077911
playwright-standard is a skill published in the GitHub repository neverinfamous/memory-journal-mcp (20 stars, last pushed 3mo ago), licensed MIT. It adds 116 tokens to every session and 705 once invoked, about $0.0005 per session on Opus 5.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
sidekick-audit
Deterministic UI quality audit of a web page or a whole product — WCAG 2.2 A/AA accessibility (axe-core), Core Web Vitals (LCP/CLS), browser health (console errors, failed requests, mixed content) and tap-target size — reported dimensions-first, with confirmed-vs-uncertain findings clustered into root-cause families…
sidekick-test
Goal-based end-to-end UI testing that PROVES the outcome. Given a URL and a plain-language goal (e.g. 'sign up, create a project, and invite a teammate'), sidekick drives a real browser to do it and then verifies success with a DETERMINISTIC signal on the real page — the execution agent is never allowed to grade its…
06-test
Write and iterate developer-side tests until they pass, or validate a user journey end to end in the browser during implementation. Use when the user wants to add coverage, find what's untested, or walk a flow while building it. Do NOT use for independent acceptance QA or reviewer evidence, auditing test health, or…
test-writer
Write tests with TDD following structured patterns. Ensures consistent AAA structure, proper coverage targets, and framework-specific conventions. Without this skill, tests lack consistent naming, miss coverage targets, and skip anti-pattern checks.
e2e-setup
Set up Playwright e2e automation tailored to this team and app. Probes the running app (auth mechanism, API surface, spec availability), interviews with recommendations instead of open questions, scaffolds the playwright/ folder, and records every decision in playwright/AUTOMATION.md for the other e2e skills to read.…
verify-fix
Re-test a bug fix after a developer resolves it. Pulls the original bug from Jira, re-executes the repro steps in the browser, checks for regressions, and updates the bug status. The final step in the SDT workflow before a ticket moves to Done. Use when: "verify fix", "retest", "is this fixed?", "check BUG-123"…