agentic-playwright: Instructions file for GitHub Copilot

.github/instructions/fixtures.instructions.md

agentic-playwright fixtures.instructions.md is an instructions file for GitHub Copilot from idavidov13/agentic-playwright. It costs 2,043 tokens per session, scanned A, original, MIT.

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

Written for GitHub Copilot: a Copilot instructions file.

This is idavidov13/agentic-playwright's own configuration. It tells GitHub Copilot how to work on agentic-playwright itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agentic-playwright configures →

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is import { test as apiRequestFixture } from '../api/api-request-fixture';.

Reuse

Borrowing it

Nothing to install: this file belongs to idavidov13/agentic-playwright. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/idavidov13/agentic-playwright/main/.github/instructions/fixtures.instructions.md
Clone the repo
git clone --depth 1 https://github.com/idavidov13/agentic-playwright

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for agentic-playwright fixtures.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/fixtures/github.svg)](https://agentmods.dev/instructions/idavidov13/agentic-playwright/fixtures)
Your own site
<a href="https://agentmods.dev/instructions/idavidov13/agentic-playwright/fixtures"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/fixtures/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.

agentmods 80×15 button for agentic-playwright fixtures.instructions.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/idavidov13/agentic-playwright/fixtures"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/fixtures.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.02043 $0.02043
Opus 5.5 $0.00817 $0.00817
Sonnet 5.5 $0.00409 $0.00409
Haiku 4.5 $0.00204 $0.00204

Measured 1mo ago against content hash 0d8b9dcec4d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.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. 1mo 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 (241 stars, last pushed 3d ago), licensed MIT. It adds 2,043 tokens to every session, about $0.0082 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.

Related

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).

microsoft/vscode · 9,715 tokens

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.

vercel/next.js · 7,581 tokens

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).

microsoft/vscode · 5,262 tokens

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.

langchain-ai/langchain · 4,680 tokens

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).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens