agentic-playwright fixtures.instructions.md

A set of rules for using Playwright fixtures to provide shared test dependencies and manage setup and cleanup. A fixture prepares data or objects for a test and can clean them up afterward, even when the test fails.

In plain words
What is it for?
Use it when adding page-object dependencies, setup and teardown routines, typed test fixtures, or new fixture categories to a Playwright project.
Why use it?
It prevents tests from creating dependencies manually or mixing reusable helpers with setup logic, which keeps test construction and cleanup consistent.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/idavidov13/agentic-playwright/fixtures
Clone the repo
git clone --depth 1 https://github.com/idavidov13/agentic-playwright

Made for: GitHub Copilot.

Per session 2,043 This file is loaded in full into every session.
When invoked 2,043 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.02043 $0.02043
Opus 5 $0.01022 $0.01022
Sonnet 5 $0.00409 $0.00409
Haiku 4.5 $0.00204 $0.00204

Measured 2d ago against content hash 0d8b9dcec4d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

agentic-playwright fixtures.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 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.

.github/instructions/fixtures.instructions.md · 176 lines

How it starts

The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Fixtures and Dependency Injection

Critical

  • ALWAYS use fixtures for dependency injection. NEVER instantiate a page object manually in a test file (new AppPage(page) is forbidden).
  • ALWAYS import test and expect from fixtures/pom/test-options.ts. NEVER import them from @playwright/test in spec files.
  • Page object fixtures live in fixtures/pom/page-object-fixture.ts. Do not create per-page fixture files.
  • Lifecycle (setup/teardown) fixtures live in fixtures/helper/helper-fixture.ts. They use the Playwright use() callback pattern.
  • Plain utility functions (no fixture lifecycle) live in helpers/ — not in fixtures/. See the helpers skill.
  • Every new fixture must be typed: extend FrameworkFixtures (for page objects) or HelperFixtures (for lifecycle) — do not add untyped fixtures.
  • Teardown uses use(). Setup runs before use(), data is yielded via use(data), teardown runs after use() — even if the test fails.
  • New fixture categories (not page objects, not lifecycle helpers) must be declared in their own fixtures/{category}/{name}-fixture.ts file and merged into test-options.ts via mergeTests().
  • Do not promote one-off API calls to helper fixtures. Helper fixtures are reserved for setup/teardown reused across 3+ spec files — see the api-testing skill (Phase 8).

Fixture Architecture

fixtures/pom/test-options.ts              ← Single import point (merges all fixtures)
    ├── fixtures/pom/page-object-fixture.ts       ← Page object fixtures
    ├── fixtures/api/api-request-fixture.ts       ← API request fixture (apiRequest for tests)
    └── fixtures/helper/helper-fixture.ts         ← Setup/teardown fixtures (important recurring operations)

test-options.ts uses mergeTests() to combine fixture layers:

import { test as base, mergeTests, request } from '@playwright/test';
import { test as pageObjectFixture } from './page-object-fixture';
import { test as apiRequestFixture } from '../api/api-request-fixture';
import { test as helperFixture } from '../helper/helper-fixture';

const test = mergeTests(pageObjectFixture, apiRequestFixture, helperFixture);
const expect = base.expect;
export { test, expect, request };

Read the full file on GitHub · 176 lines

Changes

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.

  1. 2d ago First seen · 176 lines · 2,043 tokens per session scan A 0d8b9dcec4d3

Subscribe to this mod's changes

agentic-playwright fixtures.instructions.md is an instructions file published in the GitHub repository idavidov13/agentic-playwright (139 stars, last pushed 6d ago), licensed MIT. It adds 2,043 tokens to every session, about $0.0102 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.