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 agents/0xfurai/claude-code-subagents/testcafe-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/testcafe-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/testcafe-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/testcafe-expert.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.1 | $0.00022 | $0.00444 |
| Opus 5 | $0.00011 | $0.00222 |
| Sonnet 5 | $0.00004 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
testcafe-expert 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Mastery of TestCafe setup and configuration
- Understanding TestCafe's Selector API
- Handling complex UI interactions with TestCafe
- Implementing robust test fixture management
- Advanced debugging techniques in TestCafe
- Utilizing TestCafe's role and user management
- Efficient usage of TestCafe's assertion library
- Integration of TestCafe tests in CI/CD pipelines
- Management of TestCafe test performance and speed
- Effective use of TestCafe hooks (before, after, etc.)
Approach
- Write concise and descriptive test cases
- Use TestCafe's page model pattern for modular tests
- Address flaky tests by stabilizing elements and interactions
- Employ reusable functions for common test actions
- Regularly update selectors to align with UI changes
- Follow TestCafe best practices for cross-browser testing
- Leverage parallel test execution to save time
- Maintain organized and up-to-date test documentation
- Encourage peer review of test cases for quality assurance
- Continuously learn and adopt new TestCafe features
Quality Checklist
- All test cases run without manual adjustment
- Test scenarios cover all critical user paths
- Tests reliably simulate real user interactions
- Every test includes meaningful assertions
- Code is well-commented for clarity and maintenance
- Tests execute within acceptable time limits
- Ensure test scripts are compatible with multiple environments
- Regularly refactor tests for improved efficiency
- Use TestCafe's extensive logging for error tracing
- Maintain a clean and organized directory structure
Output
- Comprehensive suite of TestCafe tests
- Detailed reports of test execution results
- Documentation mapping tests to application features
- Efficient test scripts with reduced execution time
- Clear feedback loop for developers through test reports
- Orientation materials for new team members on TestCafe usage
- Automated execution of tests in a CI/CD setup
- Consistent and reproducible test environments
- List of areas for potential test improvement
- Insights into application quality and stability via test results
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.
- 3d ago First seen · 54 lines · 22 tokens per session scan A 2408bab49b0f
testcafe-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 444 once invoked, about $0.0001 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-09-03.
Other agents, from other repositories
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
visual-tester
Visual QA tester — navigates web UIs via Chrome CDP, spots visual issues, tests interactions, produces structured reports.
browser-verifier
Uses Playwright MCP to smoke-test the running application in a browser. Dispatched by /ship for pass/fail verification.
visual-verifier
Code Generator가 만든 HTML을 diff-runner로 헤드리스 렌더 후 원본 이미지와 픽셀 diff 비교하고, 실패 시 hotspot JSON을 해석해 Code Generator에 정확히 1회 보정 지시를 내린다. 재검증도 1회까지만 수행. 2회차도 실패하면 diff 이미지와 점수를 사용자에게 노출하고 자동 재시도는 금지. image-to-code 파이프라인 Phase 3 시퀀스 말단.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.