Borrowing it
Nothing to install: this file belongs to agigante80/actual-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/agigante80/actual-mcp-server/main/.github/instructions/playwright-tests.instructions.mdgit clone --depth 1 https://github.com/agigante80/actual-mcp-serverWrote 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/instructions/agigante80/actual-mcp-server/playwright-tests)<a href="https://agentmods.dev/instructions/agigante80/actual-mcp-server/playwright-tests"><img src="https://agentmods.dev/badge/instructions/agigante80/actual-mcp-server/playwright-tests/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/instructions/agigante80/actual-mcp-server/playwright-tests"><img src="https://agentmods.dev/badge/instructions/agigante80/actual-mcp-server/playwright-tests.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.00649 | $0.00649 |
| Opus 5.5 | $0.00260 | $0.00260 |
| Sonnet 5.5 | $0.00130 | $0.00130 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
actual-mcp-server playwright-tests.instructions.md 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 29d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rules for Playwright E2E test files (tests/e2e/)
Read tests/e2e/README.md Technical Guidelines before editing any file here.
These tests require a live Docker stack. Run with npm run test:e2e:docker:full,
not npm run test:e2e (which expects Docker-internal hostnames from the host).
Run npm run typecheck:e2e after editing: Playwright transpiles specs without typechecking them.
Only npm run test:unit-js and npm run build are appropriate in Copilot's default ephemeral environment.
Key rules:
- Never hardcode server URLs or credentials — always use
process.env.MCP_SERVER_URL EXPECTED_TOOL_COUNTmust be updated to the current total whenever a tool is added or removed- File-size target: 500 lines per spec file. Files over 700 lines must be evaluated for a
split, EXCEPT
docker-all-tools.e2e.spec.ts: #366 removed a per-domain split of exactly that file because nothing ever executed it - Do not duplicate helpers. Import transport utilities from
tests/shared/e2e-helpers.ts(andtests/shared/mcp-protocol.jsfor JS callers), and importtestplus the make* factories fromtests/e2e/fixtures.ts, instead of defining helpers locally in spec files - These are API-only tests (HTTP JSON-RPC). Do not use
page.*or any browser APIs - Do NOT add
baseURLinteraction patterns — specs callMCP_SERVER_URLdirectly - Retry logic (
retries: 2) is configured inplaywright.config.ts/playwright.config.docker.ts— don't add manual retry loops - Every test provisions its own data (#375). Ask the fixtures in
tests/e2e/fixtures.ts(async ({ mcp, makeAccount }) => ...); never read an id another test wrote, and never add a shared mutable context. A test must pass when run alone with--grep - Everything a factory creates is torn down automatically. For anything no factory owns, call
cleanup.add(CLEANUP_ORDER.<kind>, label, fn), registering it BEFORE the work so a failed assertion still tears down. There is noafterAll - Every tool that performs a mutation must read the state back and assert it, and a delete test must assert absence from the corresponding list
- Every tool with a UUID parameter needs at least one negative test using
'00000000-0000-0000-0000-000000000000'
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.
- 29d ago Changed · +2 lines · +33 tokens per session 448bfb5187a3
- 2mo ago First seen · 39 lines · 616 tokens per session scan A a3f1ad461efd
actual-mcp-server playwright-tests.instructions.md is an instructions file published in the GitHub repository agigante80/actual-mcp-server (74 stars, last pushed 3d ago), licensed MIT. It adds 649 tokens to every session, about $0.0026 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.