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 skills/idavidov13/agentic-playwright/fixturesnpx skills add idavidov13/agentic-playwright --skill fixturesgit clone --depth 1 https://github.com/idavidov13/agentic-playwrightWrote 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/skills/idavidov13/agentic-playwright/fixtures)<a href="https://agentmods.dev/skills/idavidov13/agentic-playwright/fixtures"><img src="https://agentmods.dev/badge/skills/idavidov13/agentic-playwright/fixtures.svg" alt="Measured on agentmods" 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 | $0.00156 | $0.02282 |
| Opus 5 | $0.00078 | $0.01141 |
| Sonnet 5 | $0.00031 | $0.00456 |
| Haiku 4.5 | $0.00016 | $0.00228 |
Grade A, and why
fixtures 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 4d 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 — 180 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 ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 180 lines · 156 tokens per session scan A 4b69b2779ed1
fixtures is a skill published in the GitHub repository idavidov13/agentic-playwright (159 stars, last pushed today), licensed MIT. It adds 156 tokens to every session and 2,282 once invoked, about $0.0008 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 skills, from other repositories
vindicate
Use when the user wants to write, add, fix, stabilize (flaky), refactor, run, or audit Playwright browser tests, draft requirements/stories from a recording (no tests), find test-coverage gaps, scaffold a Playwright project, or set up Playwright CI. Vindicate's guided workflow for grounded, conformant Playwright test…
editorial-illustrations
Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent. This is a GENERATIVE GUIDE, not a template gallery: it teaches the "claim -> geometry" method so any session can invent…
daily-journal
A passive daily work journal that Claude keeps FOR you so you never have to write it yourself. Append short entries after meaningful work (what was done, what you focused on, artifacts touched) to 01-daily/journal/YYYY-MM-DD.md. Run a guided reflection at night or in the morning. Use when you run /daily-journal, say…
product-ui-taste
Anti-slop skill for PRODUCT UI - dashboards, data tables, forms, multi-step flows, settings, list/detail, app shells. The agent reads the surface, budgets the frame first, and ships dense interfaces that are correct at every edge case (overflow, long labels, empty/error/loading states, i18n expansion, keyboard/a11y).…
review-cockpit
Produce and continuously maintain ONE living review document for a multi-item session — a cockpit header (Progress checklist, Working folder, Context) plus per-item review cards that you approve or request changes on directly in the doc or side panel. Use whenever a session has multiple deliverables you need to…
ultragoal
Run a large, multi-session goal (e.g. shipping a whole side product) through the full V-model closed loop, one phase at a time, with cross-session state and a final north-star acceptance gate. Ultragoals never downgrade the lane: every phase runs CP-1→CP-6 with adversarial verification. Opt-in: invoke with /ultragoal…