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/config.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/config)<a href="https://agentmods.dev/instructions/idavidov13/agentic-playwright/config"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/config/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/config"><img src="https://agentmods.dev/badge/instructions/idavidov13/agentic-playwright/config.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.02424 | $0.02424 |
| Opus 5.5 | $0.00970 | $0.00970 |
| Sonnet 5.5 | $0.00485 | $0.00485 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
agentic-playwright config.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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuration
Critical
- NEVER hardcode URLs, tokens, emails, or passwords anywhere in the scaffold. The only source of truth for env-driven values is
process.env.*, backed byenv/.env.${environment}. - NEVER hardcode endpoint paths or route strings in
config/. Paths belong inenums/{area}/*(see theenumsskill). - ALWAYS add every new env variable to
env/.env.examplewith a safe placeholder — no real secrets, no production URLs. - ALWAYS add a JSDoc comment on every config property describing the value and the backing env var.
- ALWAYS keep app-facing URLs/settings in
config/app.tsand utility/third-party services inconfig/util/util.ts. Do not create ad-hoc config files elsewhere. - NEVER commit
env/.env.dev,env/.env.staging, or any other real env file containing credentials. Onlyenv/.env.exampleis tracked.
File Locations
| Type | Directory | Purpose |
|---|---|---|
| App config | config/app.ts |
URLs and settings for the main application |
| Utility config | config/util/util.ts |
Utility / third-party service configuration |
| Env template | env/.env.example |
Tracked template — safe placeholders only |
| Env (active) | env/.env.${ENVIRONMENT} |
Real values, selected at runtime (.env.dev etc.) — untracked |
Instructions
Phase 1: Understand how env files are loaded
playwright.config.ts loads env values via dotenv at startup:
const environment = process.env.ENVIRONMENT ?? 'dev';
const environmentPath = `./env/.env.${environment}`;
dotenv.config({ path: environmentPath });
Consequences:
- Default environment is
dev(fileenv/.env.dev). - Override with a shell variable:
ENVIRONMENT=staging npx playwright test. - The selected file must exist — missing files silently load nothing and every
process.env.*becomesundefined. ENVIRONMENTitself is set at the shell level; it is not declared in any.envfile.
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 · 215 lines · 2,424 tokens per session scan A bcec01fce9c8
agentic-playwright config.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,424 tokens to every session, about $0.0097 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
multiagent-template copilot-instructions.md
Instructions for Neftedollar/multiagent-template, covering workspace structure, how to work in this repo, multi-agent pipeline, orchestrator role and escalate to human only for.
runtm copilot-instructions.md
Copilot instructions for runtm-ai/runtm, covering runtm tool instructions, critical rules, structure, adding endpoints and app/api/v1/myendpoint.py.
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.