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/ukho/ukho.githubcopilot.toolkit/playwrightgit clone --depth 1 https://github.com/UKHO/UKHO.GitHubCopilot.ToolKitWhat 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.00673 | $0.00673 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00135 | $0.00135 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
UKHO.GitHubCopilot.ToolKit playwright.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 yesterday.
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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright .NET testing guidelines
Overview
These instructions define how UI tests are authored with Playwright for .NET in this repository. The goal is resilient, accessible, low-flake tests that are easy to review and diagnose. The practices in this file are repository defaults for Playwright-based UI tests unless a documented exception applies.
Scope
Applies to: test/**/*.cs, test/**/*.csproj
- Applies when creating or updating Playwright UI tests.
- The practices in this file are defaults for Playwright-based UI testing unless a narrower file or an explicitly documented exception applies.
- When a work item needs a justified deviation from these defaults, document the reason in the relevant project or work-package documentation so the deviation remains reviewable.
- These rules are additive to
/.github/instructions/folders.instructions.md(tests live undertest/).
Instructions
MUST
-
Keep Playwright tests under
test/. -
Use one Playwright test framework per test project:
- Default to xUnit:
Microsoft.Playwright.Xunit
- Default to xUnit:
-
Prefer inheriting from
PageTestfor Playwright tests. -
Use Playwright web-first assertions (
Expect(...)) for UI assertions so checks auto-retry. -
Use
Test.StepAsync()to group interactions into meaningful steps. -
Prefer user-facing, accessibility-first locators:
GetByRole,GetByLabel,GetByPlaceholder,GetByText- Use
GetByTestIdonly when a stabledata-testidexists and role/label/text locators are not practical.
-
Rely on Playwright auto-waiting.
- Avoid explicit sleeps and time-based waits.
- Prefer waiting via assertions (for example
ToHaveTextAsync,ToBeVisibleAsync,ToHaveURLAsync).
SHOULD
- Keep one test class focused on one feature/page area.
- Name test files using
<FeatureOrPage>Tests.cs. - Use
ToMatchAriaSnapshotAsyncto validate accessibility tree structure for components where markup is expected to be stable. - Use
ToHaveURLAsyncafter navigation-triggering actions. - MCP MAY be used as an authoring aid when supported, but standard Playwright/.NET execution SHOULD remain the primary supported local and CI path.
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.
- yesterday First seen · 67 lines · 673 tokens per session scan A 50aafe6cf197
UKHO.GitHubCopilot.ToolKit playwright.instructions.md is an instructions file published in the GitHub repository UKHO/UKHO.GitHubCopilot.ToolKit (1 stars, last pushed 2mo ago), licensed MIT. It adds 673 tokens to every session, about $0.0034 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
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
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, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain 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.