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 instructions/idavidov13/agentic-playwright/ai-native-workflowgit clone --depth 1 https://github.com/idavidov13/agentic-playwrightWhat 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.02744 | $0.02744 |
| Opus 5 | $0.01372 | $0.01372 |
| Sonnet 5 | $0.00549 | $0.00549 |
| Haiku 4.5 | $0.00274 | $0.00274 |
Grade A, and why
agentic-playwright ai-native-workflow.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.
How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI-Native Workflow
Routing layer between user intent and the specialized skills that own the rules. Load first on every non-trivial task.
Critical
- Low confidence means Phase 3 is incomplete. If the would-be confidence is < 5, do NOT emit Phase 4. Return to Phase 3 and ASK the user for the missing primary inputs (URL, OpenAPI link, field list, area name). Phase 4 exists for honest trade-off decisions, not for documenting "I don't have enough data" — that belongs in a question to the user. This rule is the most leveraged in the workflow: it is what stops the agent from emitting plausible-looking plans built on guesses.
- Ask, don't invent. Never guess folder names, file paths, env-var names, enum values, credentials, or message strings.
ls,grep,playwright-cli, OpenAPI — or ask. - Refuse placeholders. Guessed selectors, unverified message strings, made-up enum values, secret-shaped strings — refuse and re-explore.
TODO/skeleton/ "to fill in later" outputs count as placeholders too — offering a "skeleton page object with TODO locators while we wait forplaywright-cli" is the same failure mode as inventing locators outright; don't. - Verify the user's premise even in Direct Mode. Before applying a one-line fix, confirm the reported defect actually exists (the typo on the cited line, the import the user wants removed, the value the user says is currently set). If the premise doesn't match the file, switch out of Direct Mode and ASK — applying a "fix" to a defect that isn't there invents a change.
- Specialized skills own the rules. This skill never restates rules from
api-testing,page-objects, etc. It tells you which skill to load and in what order. - The Constitution (the always-on instructions wrapping these skills) is the safety floor. MUST/SHOULD/WON'T tables are hard stops; they take precedence over any prose, template, or example.
- Audit-then-edit by default. For any non-trivial change, follow the 8-phase workflow below. Phase 4 (Plan + Confidence) is mandatory before Phase 6 (Apply).
- Confidence gate is required. Every Plan output must include a 1-10 confidence + rationale + unknowns block. See "Phase 4" below.
- Exploration is non-negotiable. UI →
playwright-clionly (no IDE browser MCP, no Cursor browser, noplaywright codegen). API → OpenAPI/docs first, live HTTP only as fallback. - One skill at a time. Load skills sequentially per the routing table. Don't stack 5 skills' Critical blocks before starting work.
- After any test edit, run the affected tests. On red, load
debugging— never suppress, never bump timeouts.
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 · 119 lines · 2,744 tokens per session scan A 5689f358c3e3
agentic-playwright ai-native-workflow.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,744 tokens to every session, about $0.0137 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 instructions, from other repositories
nuwax AGENTS.md
Instructions for nuwax-ai/nuwax, covering ai agent system documentation, 系统概述, ai agent 架构, 核心组件 and ai 功能特性.
qaskills AGENTS.md
Instructions for PramodDutta/qaskills, covering agents.md, project overview, common commands, run a single package and run tests in watch mode.
inspecto CLAUDE.md
Instructions for inspecto-dev/inspecto, covering inspecto — claude code development guide, project overview, monorepo structure, development phases (load each file as needed) and key architectural decisions.
qaskills CLAUDE.md
Instructions for PramodDutta/qaskills, covering claude.md, what this is, conventions (non-negotiable), commands and single package.
agentic-config AGENTS.md
Instructions for WaterplanAI/agentic-config, covering project guidelines, environment & tooling, core rules, skill triggering and content & pii.
compare-mcp CLAUDE.md
Instructions for Cristophereasygoing927/compare-mcp, covering compare-mcp, architecture, running and key decisions.