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/stefaniuk/loadout/playwright-typescriptgit clone --depth 1 https://github.com/stefaniuk/loadoutWhat 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.02646 | $0.02646 |
| Opus 5 | $0.01323 | $0.01323 |
| Sonnet 5 | $0.00529 | $0.00529 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
loadout playwright-typescript.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 — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Playwright TypeScript Test Generation Instructions 🎭
These instructions define the default engineering approach for writing production-grade end-to-end tests using Playwright with TypeScript.
They must remain applicable to:
- Web application testing with Playwright async API
- Browser automation and UI testing
- Accessibility and regression testing
- Cross-browser testing (Chromium, Firefox, WebKit)
- Component testing with Playwright
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Cross-references. For general TypeScript engineering standards (typing, error handling, code organisation), see typescript.instructions.md. This file focuses exclusively on Playwright-specific testing patterns.
Shared baseline. For language-agnostic Playwright guidance, see playwright-baseline.include.md.
Identifier scheme. Every normative rule carries a unique tag in the form [PW-TS-<prefix>-NNN], where the prefix maps to the containing section (for example QR for Quick Reference, LOC for Locators, AST for Assertions, STR for Structure). Use these identifiers when referencing, planning, or validating requirements.
0. Quick reference (apply first) 🧠
This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.
- [PW-TS-QR-001] Role-based locators: prioritise
getByRole,getByLabel,getByTextfor resilience and accessibility ([PW-TS-LOC-001]). - [PW-TS-QR-002] Web-first assertions: use auto-retrying
expectAPI withawait; avoid.toBeVisible()unless testing visibility changes ([PW-TS-AST-001]). - [PW-TS-QR-003] No hard-coded waits: rely on Playwright's built-in auto-waiting mechanisms ([PW-TS-LOC-004]).
- [PW-TS-QR-004] Use test.step(): group interactions to improve readability and reporting ([PW-TS-LOC-005]).
- [PW-TS-QR-005] Standard imports: begin files with
import { test, expect } from '@playwright/test'([PW-TS-STR-001]). - [PW-TS-QR-006] Consistent file naming: follow
<feature>.spec.tsconvention ([PW-TS-ORG-002]). - [PW-TS-QR-007] Use test.describe(): group related tests logically ([PW-TS-STR-002]).
- [PW-TS-QR-008] Avoid common anti-patterns:
waitForTimeout, missingawait,{ force: true }clicks, tests without assertions (§9).
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 · 188 lines · 2,646 tokens per session scan A 3e91dd42771e
loadout playwright-typescript.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed 4d ago), licensed MIT. It adds 2,646 tokens to every session, about $0.0132 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
apm cli.instructions.md
CLI Design Guidelines for visual output, styling, and user experience standards.
apm integrators.instructions.md
Architecture rules for file-level integrators (BaseIntegrator pattern).
apm cicd.instructions.md
CI/CD Pipeline configuration for PyInstaller binary packaging and release workflow.
spec-driven-steroids AGENTS.md
Instructions for lindoelio/spec-driven-steroids, covering agents.md, project identity, technology stack, essential commands and agent constraints.
featherspec constitution.instructions.md
FeatherSpec constitution editing rules (thin loader).
featherspec knowledge-records.instructions.md
FeatherSpec knowledge record rules — observation, rationale, provenance (thin loader).