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 instructions/idavidov13/agentic-playwright/fixturesgit clone --depth 1 https://github.com/idavidov13/agentic-playwrightWhat 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 | $0.02043 | $0.02043 |
| Opus 5 | $0.01022 | $0.01022 |
| Sonnet 5 | $0.00409 | $0.00409 |
| Haiku 4.5 | $0.00204 | $0.00204 |
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.
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
testandexpectfromfixtures/pom/test-options.ts. NEVER import them from@playwright/testin 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 Playwrightuse()callback pattern. - Plain utility functions (no fixture lifecycle) live in
helpers/— not infixtures/. See thehelpersskill. - Every new fixture must be typed: extend
FrameworkFixtures(for page objects) orHelperFixtures(for lifecycle) — do not add untyped fixtures. - Teardown uses
use(). Setup runs beforeuse(), data is yielded viause(data), teardown runs afteruse()— even if the test fails. - New fixture categories (not page objects, not lifecycle helpers) must be declared in their own
fixtures/{category}/{name}-fixture.tsfile and merged intotest-options.tsviamergeTests(). - 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-testingskill (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 };
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 · 176 lines · 2,043 tokens per session scan A 0d8b9dcec4d3
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.
Other instructions, from other repositories
llm-ide-rules pytest-integration-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest integration tests and example integration test.
e2e-skills AGENTS.md
Instructions for voidmatcha/e2e-skills, covering agents.md, repository overview, verification gate (must pass before commit), directory layout and conventions.
agentic-config AGENTS.md
Instructions for WaterplanAI/agentic-config, covering project guidelines, environment & tooling, core rules, skill triggering and content & pii.
compare-mcp CLAUDE.md
Instructions for Cristophereasygoing927/compare-mcp, covering compare-mcp, architecture, running and key decisions.
multiagent-template CLAUDE.md
Instructions for Neftedollar/multiagent-template, covering how to start (required for every session), 1. determine mode, 2. load context (depends on mode), 3. act and workspace structure.
vibe-mcp AGENTS.md
Instructions for VibeTechnologies/vibe-mcp, covering vibe-mcp agent memory, canonical eval reference, relay and connection semantics, what counts as real e2e and fake extension test harness rules.