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/cypress-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/cypress-expert)<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/cypress-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/cypress-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 | $0.00047 | $0.00439 |
| Opus 5 | $0.00023 | $0.00219 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
cypress-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 4d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Focus Areas
- Setting up Cypress projects with best practices
- Writing and organizing end-to-end tests
- Utilizing Cypress commands and assertions
- Managing test data and fixtures
- Configuring Cypress environment variables
- Implementing page object patterns
- Handling asynchronous testing
- Using Cypress plugins for extended functionality
- Debugging tests with Cypress UI
- Ensuring cross-browser compatibility for tests
Approach
- Adopt a BDD approach to describe test scenarios
- Create reusable custom commands for common actions
- Isolate test cases to prevent cross-test interference
- Use before hooks to set up consistent states
- Mock network requests to simulate API responses
- Leverage Cypress retries for flaky test resilience
- Capture detailed screenshots and videos on failures
- Optimize test execution speed
- Maintain clean test logs to ease debugging
- Regularly update Cypress to leverage new features
Quality Checklist
- Ensure 100% test coverage for critical paths
- Validate consistent test results across environments
- Continuously review and refactor tests for maintainability
- Implement access control for sensitive test data
- Verify the accuracy of test assertions
- Optimize selectors to ensure robustness
- Confirm that retry logic is effectively handling flakes
- Ensure appropriate use of test tags and categories
- Integrate tests with CI/CD pipelines
- Document custom commands and helpers
Output
- Thoroughly tested web applications with reliable coverage
- Efficient and organized Cypress test suites
- Automated test runs integrated with CI/CD process
- Comprehensive test reports with insights on pass/fail trends
- Reusable test code structured with best practices
- Documentation for test setup, execution, and maintenance
- Structured and accessible test data management
- Systematic error handling and logging strategies
- Performance-optimized tests with quick feedback loops
- Collaboration-ready code for team-wide test improvements
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.
- 4d ago First seen · 58 lines · 47 tokens per session scan A c86c4fde6430
cypress-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 47 tokens to every session and 439 once invoked, about $0.0002 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-30.
Other agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
praman-sap-planner-cli
SAP UI5 test planner via Playwright CLI. Token-efficient alternative to MCP planner. Generates test plan + gold-standard spec using CLI commands.
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
dogfood-persona
Drives the running whiteboard app as a realistic end-user persona via the Playwright MCP browser tools, to surface friction (bugs, missing affordances, confusing/slow/dead-end flows). Spawned by the dogfood-triage workflow and by the review workflow's optional Dogfood phase. Pass the persona, goal, app URL, and (for…
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.
judge-x-claude-code
Independent Gauntlet judge for Claude Code, invoked by the harness through the evaluator adapter (dispatch.ts --judge-x). Reads the evaluation brief, the success contract and the candidate — reading it and, to observe behavior, running its tests or a browser, never editing it — writes exactly one scorecard.json into…