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/enums.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/enums)<a href="https://agentmods.dev/instructions/idavidov13/agentic-playwright/enums"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/enums/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/enums"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/enums.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.02598 | $0.02598 |
| Opus 5.5 | $0.01039 | $0.01039 |
| Sonnet 5.5 | $0.00520 | $0.00520 |
| Haiku 4.5 | $0.00260 | $0.00260 |
Grade A, and why
agentic-playwright enums.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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enums
Critical
- Convention: TypeScript
enum— the scaffold uses the language constructenum, notas constobject literals. Stay consistent. - Enum name: PascalCase (e.g.,
Messages,ApiEndpoints,Roles,StorageStatePaths). - Enum member: SCREAMING_SNAKE_CASE (e.g.,
LOGIN_SUCCESS,CURRENT_USER,APP). - Location: app-defined strings go in
enums/{area}/*.ts; cross-app constants go inenums/util/*.ts. Do not invent a new top-level folder. - JSDoc: every enum declaration must have a JSDoc comment describing what the enum groups.
- No hardcoded repeat strings. Any string used in more than one place — endpoint paths, UI messages, roles, storage-state paths — must live in an enum and be imported.
- Message values must match the real app. For enums that mirror UI text (error messages, success messages, validation text), the string must be captured via
playwright-clifrom the live app, not guessed. - Edits to existing enum values go through
refactor-values. Renaming a key or changing a value cascades through tests, page objects, and schemas.
File Locations
{area}is a placeholder. Before creating or referencing any path below, runls enums/to discover the real subdirectory names in this repo (e.g.,front-office,back-office) and use those instead.
| Type | Directory | Naming | Scaffold examples |
|---|---|---|---|
| App-specific enums | enums/{area}/ |
[name].ts |
Messages, ApiEndpoints, StorageStatePaths (in enums/app/app.ts) |
| Shared / utility enums | enums/util/ |
[name].ts |
Roles (in enums/util/roles.ts) |
Instructions
Phase 1: Decide if the value belongs in an enum
Use this decision table. Each row points to the canonical home — use it to prevent enums/ from overlapping with config/ or test-data/static/.
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 · 181 lines · 2,598 tokens per session scan A 9e8f0fa3a437
agentic-playwright enums.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,598 tokens to every session, about $0.0104 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.