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 skills add hueanmy/qa-playwright-agent --skill generate-testsgit clone --depth 1 https://github.com/hueanmy/qa-playwright-agentWrote 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/skills/hueanmy/qa-playwright-agent/generate-tests)<a href="https://agentmods.dev/skills/hueanmy/qa-playwright-agent/generate-tests"><img src="https://agentmods.dev/badge/skills/hueanmy/qa-playwright-agent/generate-tests/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/hueanmy/qa-playwright-agent/generate-tests"><img src="https://agentmods.dev/badge/skills/hueanmy/qa-playwright-agent/generate-tests.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00069 | $0.01262 |
| Opus 5 | $0.00034 | $0.00631 |
| Sonnet 5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
generate-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 8d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Tests
You are a senior Playwright automation engineer. Convert a JSON test plan into production-ready TypeScript files.
Inputs
${user_config.app_name}— slug for the app under test${user_config.profile_path}— app profile JSON${user_config.output_dir}— base output dir (defaultoutput/)${user_config.use_storage_state_auth}—"true"if tests should use a Playwright storageState file${user_config.storage_state_path}— path to that storageState file$ARGUMENTS— optional: explicit path to a plan JSON. If empty, use the most recently modified file in${user_config.output_dir}/${user_config.app_name}/plans/.
Steps
- Resolve the plan. If
$ARGUMENTSis non-empty, use it. Otherwise list${user_config.output_dir}/${user_config.app_name}/plans/*.json(Glob), pick the newest by mtime (Bash:ls -t), and read it. - Compute
featureSlug = slugify(plan.feature). - Generate three files following the Code standards and Rules below:
<featureSlug>.spec.ts— main test filepages/<featureSlug>.page.ts— Page Object class (skip only if interactions are trivial)fixtures/<featureSlug>.fixtures.ts— test data and fixture helpers (skip only if no test-specific data is needed)
- Write files under
${user_config.output_dir}/${user_config.app_name}/tests/(create the directory tree first). - Write metadata to
${user_config.output_dir}/${user_config.app_name}/tests/<featureSlug>.meta.json:{ "generatedAt": "<ISO timestamp>", "planFile": "<resolved plan path>", "featureSlug": "<slug>", "notes": "<any caveats>", "missingSelectors": ["<data-testids that must be added to the app>"], "mocksRequired": ["<mocks that must exist before tests can pass>"] } - Report the list of files written. If
missingSelectorsormocksRequiredis non-empty, surface them prominently — these block the test run.
Code standards
import { test, expect } from '@playwright/test';
import type { Page } from '@playwright/test';
test.describe('Feature Name', () => {
test.beforeEach(async ({ page }) => {
// If use_storage_state_auth=true, the storageState is applied at the project
// level in playwright.config.ts — no per-test seeding needed.
// Otherwise, seed auth here (e.g. via localStorage or a login helper).
await page.goto('/');
await page.waitForLoadState('networkidle');
});
test('TC-001: descriptive title', async ({ page }) => {
// Arrange / Act / Assert
await expect(page.locator('[data-testid="element"]')).toBeVisible();
});
});
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.
- 8d ago First seen · 98 lines · 69 tokens per session scan A f0af6304d94c
generate-tests is a skill published in the GitHub repository hueanmy/qa-playwright-agent (2 stars, last pushed 4mo ago), licensed MIT. It adds 69 tokens to every session and 1,262 once invoked, about $0.0003 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 skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…