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.
curl -O https://raw.githubusercontent.com/idavidov13/agentic-playwright/main/.github/instructions/data-strategy.instructions.mdgit 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/instructions/idavidov13/agentic-playwright/data-strategy)<a href="https://agentmods.dev/instructions/idavidov13/agentic-playwright/data-strategy"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/data-strategy/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/idavidov13/agentic-playwright/data-strategy"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/data-strategy.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.02684 | $0.02684 |
| Opus 5.5 | $0.01074 | $0.01074 |
| Sonnet 5.5 | $0.00537 | $0.00537 |
| Haiku 4.5 | $0.00268 | $0.00268 |
Grade A, and why
agentic-playwright data-strategy.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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Strategy
This framework uses a bifurcated data strategy: static data for deterministic curated cases and dynamic factories for test isolation.
Critical
- Static data files are TypeScript only. Every file under
test-data/static/**is a.tsfile that exportsas constliteral values. NEVER use.json. - Static data files may only export literal values. No runtime imports (type-only imports are fine), no function definitions, no computed values, no Faker calls. Dynamic data belongs in factories, not in static files.
- NEVER hardcode test content strings (names, emails, todo text, product names, descriptions, etc.) in a spec file. Generate with a Faker factory.
- NEVER redefine universal type-mismatch arrays (
[123, true, null, undefined], etc.) inline. Import them fromtest-data/static/util/invalid-values.ts. - ALWAYS validate factory output with
Schema.parse(...)and return the Zod-inferred type. - NEVER generate app-defined strings with Faker (error messages, button labels, page headers). Those live in
enums/so they stay in sync with the application under test. - NEVER store fixed expected values that are used in a single assertion in a static data file. Keep them inline in the test.
- ALWAYS follow the
refactor-valuesskill before editing any existing static-data file or enum value — these edits cascade through assertions and data-driven loops. - NEVER introduce magic numbers (timeouts, retry counts, limits) inline. Prefer web-first assertions; when a numeric value is unavoidable, route it through
playwright.config.tsor an enum inenums/.
File Locations
{area}is a placeholder. Before creating or referencing any path below, runls test-data/static/andls test-data/factories/to discover the real subdirectory names in this repo (e.g.,front-office,back-office) and use those instead.
| Type | Directory | Purpose |
|---|---|---|
| Universal invalid arrays | test-data/static/util/ |
Type-mismatch tuples reused by every negative test (.ts, as const) |
| Domain-specific static | test-data/static/{area}/ |
Curated invalid/boundary sets tied to the app's validation rules (.ts, as const) |
| Dynamic factories | test-data/factories/{area}/ |
Faker + Zod factories for unique, valid data per test run |
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 · 232 lines · 2,684 tokens per session scan A 5637b1186f40
agentic-playwright data-strategy.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,684 tokens to every session, about $0.0107 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.
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).
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).
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.