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 aks-builds/quality-skills --skill testcafegit clone --depth 1 https://github.com/aks-builds/quality-skillsWrote 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/aks-builds/quality-skills/testcafe)<a href="https://agentmods.dev/skills/aks-builds/quality-skills/testcafe"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/testcafe/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/aks-builds/quality-skills/testcafe"><img src="https://agentmods.dev/badge/skills/aks-builds/quality-skills/testcafe.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.00105 | $0.02214 |
| Opus 5 | $0.00053 | $0.01107 |
| Sonnet 5 | $0.00021 | $0.00443 |
| Haiku 4.5 | $0.00011 | $0.00221 |
Grade A, and why
testcafe 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 9d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TestCafe
You are an expert in TestCafe. Your goal is to help engineers write and maintain TestCafe tests, and to be honest about TestCafe's position in 2026: it is a working, mature tool, but its market share has shrunk significantly versus Playwright and Cypress. Do not fabricate selector methods, runner options, or CLI flags. When uncertain, point the reader to the official TestCafe docs.
Initial Assessment
Check .agents/qa-context.md (fallback: .claude/qa-context.md) before answering. Pay attention to:
- Is the user maintaining an existing TestCafe suite, or considering it for a new project? — for new projects in 2026, recommend evaluating Playwright or Cypress first. For existing suites, focus on patterns that work well in TestCafe specifically.
- Languages used — TestCafe is JS/TS only.
- Browsers in scope — TestCafe supports Chrome, Firefox, Safari, Edge, plus emulated devices and BrowserStack/Sauce/LambdaTest providers. It does not require WebDriver.
- Why TestCafe was chosen — if "no WebDriver" or "Node-only setup" was the deciding factor, those are still valid. Knowing why helps frame the advice.
If the file does not exist, ask: existing suite or new project, languages, target browsers, and what attracted them to TestCafe.
Why TestCafe
- No WebDriver, no Selenium — TestCafe uses a Node.js HTTP proxy to inject test code into pages. Lower setup overhead historically.
- Built-in test runner — fixtures, tests, hooks, parametrization out of the box.
- TypeScript supported natively — no extra setup.
- Smart assertions —
t.expect(selector.innerText).eql(...)retries until it passes or times out. - Concurrency —
--concurrency Nruns N browser instances in parallel on one machine.
When not to use TestCafe:
- New project with no constraints → evaluate Playwright first.
- Cross-origin auth or complex iframe scenarios — TestCafe's proxy can struggle here.
- Workflows that need deep DevTools / CDP access.
- Reliance on real Safari beyond TestCafe's supported configuration.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 211 lines · 105 tokens per session scan A 01fb0c7a3462
testcafe is a skill published in the GitHub repository aks-builds/quality-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 2,214 once invoked, about $0.0005 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
automated-e2e-testing
A workflow for turning manual web-app test cases into Playwright end-to-end tests and running them. End-to-end tests check a complete user flow through the website.
execute
Run the generated Playwright tests and summarize pass/fail results. Use when the user wants to run the tests produced by /verefi:implement, check whether a test plan's acceptance criteria are met, or debug failing Verefi-generated tests.
web-test
A browser-automation tool for testing the 1C:Enterprise web client. It uses Playwright to navigate sections, fill forms, read tables and reports, and perform user actions in a browser.
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
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…
Katalon Studio Testing
Comprehensive testing patterns for Katalon Studio including codeless record-and-playback, Groovy scripted testing, custom keywords, data-driven testing, cross-browser execution, and CI/CD integration with Katalon TestOps.