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/jpbaking/playwright-fieldkit/agents-mdgit clone --depth 1 https://github.com/jpbaking/playwright-fieldkitWhat 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.00181 | $0.00181 |
| Opus 5 | $0.00090 | $0.00090 |
| Sonnet 5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
playwright-fieldkit AGENTS.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.
What it actually says
Playwright FieldKit repository instructions
Follow the Portable Agent Authoring guides for every skill or harness change.
- Edit the portable skill only under
.agents/skills/pw-playwright-fieldkit/. - Regenerate
.claude/skills/pw-playwright-fieldkit/byte-identically, excluding only machine-localscripts/node_modules/. - Keep
.clinerules/workflows/pw-playwright-fieldkit.mdas a thin skill invocation shim; detailed procedures belong inreferences/workflows/. - Keep the distributable intent rule in
rules/shared/pw-playwright-fieldkit.mdand preserve the authorized-target boundary. - Run
npm testfrom the authoritative skill'sscripts/directory after changing scripts or workflow contracts.
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 · 18 lines · 181 tokens per session scan A 1a2d2f2487d9
playwright-fieldkit AGENTS.md is an instructions file published in the GitHub repository jpbaking/playwright-fieldkit (2 stars, last pushed 1mo ago), licensed MIT. It adds 181 tokens to every session, about $0.0009 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
playwright CLAUDE.md
Claude Code instructions for microsoft/playwright, covering monorepo packages, browser packages, tooling packages, key directories and build.
playwright copilot-instructions.md
Copilot instructions for microsoft/playwright, a project described as: Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
argus AGENTS.md
Instructions for chriswu727/argus, covering argus — agent guide, setup, web mode (works everywhere), wire it into the mcp host and using argus within the host task.
claude-browser-test-skills CLAUDE.md
Instructions for Autodesk/claude-browser-test-skills, covering claude.md, what this repo is, layout, conventions when editing skills and validate before publishing.
sniff AGENTS.md
Instructions for Aboudjem/sniff, covering agents.md: sniff, what this repo is, how an agent should use sniff, handling the playwright setup gate and finding output schema.
AI-Watch-Tester CLAUDE.md
Instructions for ksgisang/AI-Watch-Tester, covering aat (ai auto tester) — project guide, ⛔ awt testing workflow (필수 준수), step 1: scan, step 2: generate + present and step 3: execute (승인 후에만).