Borrowing it
Nothing to install: this file belongs to stefaniuk/loadout. 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/stefaniuk/loadout/main/.github/instructions/playwright-python.instructions.mdgit clone --depth 1 https://github.com/stefaniuk/loadoutWrote 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/stefaniuk/loadout/playwright-python)<a href="https://agentmods.dev/instructions/stefaniuk/loadout/playwright-python"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/playwright-python/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/stefaniuk/loadout/playwright-python"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/playwright-python.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.02443 | $0.02443 |
| Opus 5.5 | $0.00977 | $0.00977 |
| Sonnet 5.5 | $0.00489 | $0.00489 |
| Haiku 4.5 | $0.00244 | $0.00244 |
Grade A, and why
loadout playwright-python.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 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 — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright Python Test Generation Instructions 🎭
These instructions define the default engineering approach for writing production-grade end-to-end tests using Playwright with Python.
They must remain applicable to:
- Web application testing with Playwright sync API
- Browser automation and UI testing
- Accessibility and regression testing
- Cross-browser testing (Chromium, Firefox, WebKit)
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Cross-references. For general Python engineering standards (typing, error handling, code organisation), see python.instructions.md. This file focuses exclusively on Playwright-specific testing patterns.
Shared baseline. For language-agnostic Playwright guidance, see playwright-baseline.include.md.
Identifier scheme. Every normative rule carries a unique tag in the form [PW-PY-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, LOC for Locators, AST for Assertions, STR for Structure). Use these identifiers when referencing, planning, or validating requirements.
0. Quick reference (apply first) 🧠
This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.
- [PW-PY-QR-001] Role-based locators: prioritise
get_by_role,get_by_label,get_by_textfor resilience and accessibility ([PW-PY-LOC-001]). - [PW-PY-QR-002] Web-first assertions: use auto-retrying
expectAPI; avoid.to_be_visible()unless testing visibility changes ([PW-PY-AST-001]). - [PW-PY-QR-003] No hard-coded waits: rely on Playwright's built-in auto-waiting mechanisms ([PW-PY-LOC-004]).
- [PW-PY-QR-004] Descriptive test titles: use clear, intent-revealing function names ([PW-PY-STR-004]).
- [PW-PY-QR-005] Standard imports: begin files with
from playwright.sync_api import Page, expect([PW-PY-STR-001]). - [PW-PY-QR-006] Consistent file naming: follow
test_<feature>.pyconvention ([PW-PY-ORG-002]). - [PW-PY-QR-007] Prefer expect over assert: use Playwright's
expectfor more reliable UI tests ([PW-PY-AST-004]). - [PW-PY-QR-008] Avoid common anti-patterns:
time.sleep(),force=Trueclicks, shared mutable state, tests without assertions (§9).
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 · 172 lines · 2,443 tokens per session scan A d0cffb29a264
loadout playwright-python.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 2,443 tokens to every session, about $0.0098 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-31.
Other instructions, from other repositories
ai-agent-rules-generator browsetools.instructions.md
Browser verification rules for Glitch WooCommerce Payment Gateway using Chrome DevTools MCP.
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).