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 whitebeardit/.cursor --skill skill-qa-playwright-add-test-datagit clone --depth 1 https://github.com/whitebeardit/.cursorWrote 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/whitebeardit/.cursor/skill-qa-playwright-add-test-data)<a href="https://agentmods.dev/skills/whitebeardit/.cursor/skill-qa-playwright-add-test-data"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-qa-playwright-add-test-data/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/whitebeardit/.cursor/skill-qa-playwright-add-test-data"><img src="https://agentmods.dev/badge/skills/whitebeardit/.cursor/skill-qa-playwright-add-test-data.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.00060 | $0.00527 |
| Opus 5.5 | $0.00024 | $0.00211 |
| Sonnet 5.5 | $0.00012 | $0.00105 |
| Haiku 4.5 | $0.00006 | $0.00053 |
Grade A, and why
qa-playwright-add-test-data 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 1mo 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
Add test data (inputs and builders)
When adding or extending test data for a flow, follow this structure.
Where
- API flow:
test-data/api/<fluxo>/ - UI flow:
test-data/ui/<fluxo>/
Static inputs (inputs.json)
- Create or edit
inputs.json(orinputs.ts) with entries per scenario (e.g.getPost,createPost; orformUrl,sobreVoce). - In the spec, import:
import inputs from '../../../test-data/<api|ui>/<fluxo>/inputs.json';and use (e.g.inputs.getPost,inputs.sobreVoce).
Example: test-data/api/hello/inputs.json, test-data/ui/whitebeard/inputs.json.
Generated data (builder.ts, optional)
- When you need to vary data (e.g. unique email per run), add
builder.tsin the same flow folder. - Export a function that builds a default object and accepts overrides; use lib/data-factory.ts (randomEmail, randomString, randomNumber) inside the builder.
- In the spec, import the builder and call it (e.g.
createFormInput({ email: randomEmail() })).
Example: test-data/ui/whitebeard/builder.ts.
Checklist
- Folder exists under
test-data/api/<fluxo>/ortest-data/ui/<fluxo>/ - inputs.json (or inputs.ts) defines static cases; builder.ts only if varying data is needed
- Spec imports from
../../../test-data/...(three levels up fromtests/<api|ui>/<fluxo>/)
Full reference
docs/04-test-data.md — inputs and builders
docs/05-lib.md — lib/data-factory (randomString, randomEmail, randomNumber)
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.
- 1mo ago First seen · 40 lines · 0 tokens per session scan A e4335787b0ad
qa-playwright-add-test-data is a skill published in the GitHub repository whitebeardit/.cursor (12 stars, last pushed 7mo ago), licensed MIT. It adds 60 tokens to every session and 527 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
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.
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
critique
Adversarial design critique of the current work — render it, look at it, and argue for rejection. Run after the gates are green, never instead of them.