What is agentic-playwright enums.instructions.md?

Rules for storing repeated application values in TypeScript enums, which are named groups of fixed values. It defines naming, file locations, documentation, and how to verify values that mirror messages shown by the application.

Use it when adding or changing endpoint paths, roles, storage paths, UI messages, validation text, or other shared application values.

It prevents repeated strings, guessed UI messages, and inconsistent constants from spreading through tests and page objects. It also provides one place to update values used in multiple files.

agentic-playwright enums.instructions.md — Instructions file by idavidov13

Install

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.

agentmods

npx agentmods add instructions/idavidov13/agentic-playwright/enums

Clone the repo

git clone --depth 1 https://github.com/idavidov13/agentic-playwright

Made for: GitHub Copilot.

Per session 2,598 This file is loaded in full into every session.

When invoked 2,598 The same file — it is already loaded in full.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.02598	$0.02598
Opus 5	$0.01299	$0.01299
Sonnet 5	$0.00520	$0.00520
Haiku 4.5	$0.00260	$0.00260

Measured 2d ago against content hash 9e8f0fa3a437, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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

.github/instructions/enums.instructions.md · 181 lines

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 construct enum, not as const object 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 in enums/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-cli from 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, run ls 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/.

Read the full file on GitHub · 181 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.

2d ago First seen · 181 lines · 2,598 tokens per session scan A 9e8f0fa3a437

Subscribe to this mod's changes

agentic-playwright enums.instructions.md is an instructions file published in the GitHub repository idavidov13/agentic-playwright (139 stars, last pushed 5d ago), licensed MIT. It adds 2,598 tokens to every session, about $0.0130 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.

Languages TypeScript agentic ai api-testing claude-code cursor e2e

COG-second-brain AGENTS.md

Instructions for huytieu/COG-second-brain, covering cog: agentic second brain - universal agent commands, available commands, /onboarding, /braindump and /daily-brief.

huytieu/COG-second-brain · 11,064 tokens

COG-second-brain CLAUDE.md

Instructions for huytieu/COG-second-brain, covering cog second brain — framework instructions, verification harness (opt-in, off by default), visual verification (always apply, ui/ux tasks), delegation cap (always apply) and model routing — always apply.

huytieu/COG-second-brain · 4,002 tokens

agentic-playwright enums.instructions.md