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 rules/yudefine/nuxt-supabase-starter/playwright-webservergit clone --depth 1 https://github.com/YuDefine/nuxt-supabase-starterWrote 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/rules/yudefine/nuxt-supabase-starter/playwright-webserver)<a href="https://agentmods.dev/rules/yudefine/nuxt-supabase-starter/playwright-webserver"><img src="https://agentmods.dev/badge/rules/yudefine/nuxt-supabase-starter/playwright-webserver.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.00000 | $0.03008 |
| Opus 5 | $0.00000 | $0.01504 |
| Sonnet 5 | $0.00000 | $0.00602 |
| Haiku 4.5 | $0.00000 | $0.00301 |
Grade A, and why
playwright-webserver 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.
How it starts
The opening of the file, as written. The whole thing — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright webServer 必 CI-safe
核心命題：E2E 的 webServer 啟動 command 會在 CI 乾淨環境跑 —— actions/checkout
的 repo 沒有 .env、沒有 tunnel creds、port 配置可能跟本地不同。webServer 的 CI 路徑
MUST 能在這個環境起來，不可依賴任何本地 dev-only 條件。違反時 Playwright 只會回不透明
的 Process from config.webServer was not able to start. Exit code: 1（webServer 子程序
的 stderr 被 Playwright 吞掉），現場無 stack，極難判讀。
真相層：本檔規範
playwright*.config.ts的webServer/use.nuxt啟動契約。dev 環境本身的 tunnel / port convention 是 [[dev-tunnel-convention]] / [[dev-port-allocation]] 的事；test 內容反模式（mock 濫用、boundary）是 [[testing-anti-patterns]] 的事。三者不重疊。對應 pitfall：
pitfall-playwright-webserver-pnpm-dev-tunnel-ci-exit1（~/offline/clade/docs/pitfalls/2026-06-11-playwright-webserver-pnpm-dev-tunnel-ci-exit1.md）。
MUST
- webServer 的 CI 路徑走 production-ish server：用
@nuxt/test-utils的use.nuxt.dev: false（CI 自動 build + 起 server）或手動webServer.command在 CI 分支跑nuxt preview。NEVER 在 CI 路徑碰 dev tunnel / 多程序 dev script。 reuseExistingServer: !process.env.CI（手動 webServer 時）。CI 一律全新啟動，本地才 重用已開的 server。- port 對齊：
webServer.url/baseURL的 port 必須跟 server 實際聽的 port 一致 （手動 command 顯式帶--port <N>）。Nuxtpreview預設聽 3000，consumer 多半不是 3000 → 不顯式帶 port 會 connect 不到 → timeout。port 來源見 [[dev-port-allocation]]。
NEVER
- ❌
webServer.command: 'pnpm dev'（或任何 dev script），當該 command 沒有process.env.CI ?分支把 CI 導向非-dev 啟動方式時。尤其 dev script 經concurrently -k包了 tunnel / migration / 多個子程序：CI 缺.env/ creds → 子程序process.exit(1)→concurrently -k（kill-others-on-fail）連坐打掉整組 → webServer exit 1，約 2 秒內快速失敗，stderr 被吞，無從判讀。 - ❌
reuseExistingServer: true（無條件重用）。CI 沒有「既有 server」可重用，且本地殘留的 舊 server 會讓 E2E 跑在過時 build 上。 - ❌ 把 E2E 紅燈當「之後再看」——
workflow_run觸發 + 非 required check 的 E2E job 紅燈 長期被忽略 = false confidence（以為有 E2E gate，實際從未綠過）。webServer 起不來的 紅燈要當天 root-cause。
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 · 199 lines · 0 tokens per session scan A 3c99af183ff1
playwright-webserver is a cursor rule published in the GitHub repository YuDefine/nuxt-supabase-starter (45 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,008 tokens. 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-09-03.
Other cursor rules, from other repositories
test-engineer
When designing test strategy, analysing coverage, or writing tests outside the TDD cycle. Also use when working with CI pipelines or validating changes end-to-end.
80-testing-ci-release
Testes Vitest/e2e, fixtures, CI e release.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.