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 commands/openva/richmondsunlight.com/run-browser-testsgit clone --depth 1 https://github.com/openva/richmondsunlight.comWrote 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/commands/openva/richmondsunlight.com/run-browser-tests)<a href="https://agentmods.dev/commands/openva/richmondsunlight.com/run-browser-tests"><img src="https://agentmods.dev/badge/commands/openva/richmondsunlight.com/run-browser-tests.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00111 |
| Opus 5 | $0.00000 | $0.00056 |
| Sonnet 5 | $0.00000 | $0.00022 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
run-browser-tests 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
Run the Playwright browser test suite inside Docker.
docker compose run --rm -e PLAYWRIGHT_BASE_URL="http://rs_web" -e PLAYWRIGHT_BROWSERS_PATH=/workspace/.pw-browsers -e PLAYWRIGHT_API_BASE_URL="http://api" -v $(pwd)/.pw-browsers:/workspace/.pw-browsers --workdir /workspace/deploy/browser-tests playwright bash -lc "npm ci --ignore-scripts && npx playwright install chromium && npx playwright test"
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 · 6 lines · 0 tokens per session scan A f3cdf3c914ca
run-browser-tests is a command published in the GitHub repository openva/richmondsunlight.com (16 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 111 tokens. 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-09-01.
Other commands, from other repositories
e2e
使用 Playwright 对 Web UI 进行端到端测试（支持视频录制、Trace 录制、控制台/网络日志捕获）.
plan-spec
仅在人工明确安排 UI 自动化时，根据任务、产品规则或原型生成独立行为 Spec.
generate_application_test_plan
Khám phá ứng dụng web, sinh test plan và test scenarios. Hỗ trợ 2 mode — PLAN (chỉ test plan) và FULL (test plan + automation skeleton).
open
SoDam-Design-Kit open 대시보드 — 검증 이력·판정서·스크린샷을 브라우저로 열람 + 재검증.
playwright-cli
Use this skill whenever the user wants to automate a browser, scrape web content, take screenshots or PDFs of pages, fill out forms, click through UI flows, or run end-to-end tests — without using an MCP server. This skill drives Playwright directly from the bashtool via Node.js scripts. Trigger whenever the user says…
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.