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 rules/verdexhq/verdex-mcp/workflow-discovery-guidegit clone --depth 1 https://github.com/verdexhq/verdex-mcpWrote 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/rules/verdexhq/verdex-mcp/workflow-discovery-guide)<a href="https://agentmods.dev/rules/verdexhq/verdex-mcp/workflow-discovery-guide"><img src="https://agentmods.dev/badge/rules/verdexhq/verdex-mcp/workflow-discovery-guide.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.00124 | $0.06912 |
| Opus 5 | $0.00062 | $0.03456 |
| Sonnet 5 | $0.00025 | $0.01382 |
| Haiku 4.5 | $0.00012 | $0.00691 |
Grade A, and why
workflow-discovery-guide 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 5d 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 — 1,185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Discovery & Exploration with Verdex
A comprehensive guide for interactively exploring web applications and mapping user journeys before writing production test code.
Table of Contents
- Core Philosophy
- The Exploration Workflow
- Tool Reference
- Interactive Techniques
- Workflow Documentation Patterns
- Identifying Assertion Points
- Real-World Walkthroughs
- Common Scenarios
- Troubleshooting Exploration
- Transition to Selector Writing
Core Philosophy
🎯 Workflow-First Thinking
Before writing any test code, you must understand:
- What is the user journey from start to finish?
- What actions does the user take at each step?
- What changes in the UI after each action?
- What URLs or redirects occur?
- What should be asserted to confirm success?
The Verdex Exploration Cycle
Navigate → Snapshot → Analyze → Interact → Repeat
↑ ↓
└────────────── Document Journey ────────┘
Key Principle: Use refs (e1, e2, e3...) for exploration, NOT for production code.
- Refs are temporary identifiers for interactive discovery
- They help you understand the workflow quickly
- They get replaced with stable selectors later
The Exploration Workflow
Step-by-Step Process
1. Initialize Browser Session
await browser_initialize()
Purpose: Start a fresh browser context for exploration
2. Navigate to Starting Point
await browser_navigate("https://app.example.com/login")
What to note:
- Starting URL
- Initial page state
- Any redirects (e.g., already logged in → dashboard)
3. Take Snapshot - See What's Available
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.
- 5d ago First seen · 1,185 lines · 124 tokens per session scan A 4a1d0b9eb82a
workflow-discovery-guide is a cursor rule published in the GitHub repository verdexhq/verdex-mcp (17 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 124 tokens to every session and 6,912 once invoked, about $0.0006 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 cursor rules, from other repositories
puppeteer
This guide provides opinionated, actionable best practices for writing robust, performant, and maintainable Puppeteer scripts for web scraping, automation, and testing. It emphasizes modern patterns like page.locator() and efficient resource management.
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
qa-script-executor
QA Script Executor - Executes natural language test scripts using Chrome DevTools MCP and enhances them with technical hints.
playwright
本规范强制执行 Playwright 测试的最佳实践和编码标准，包括稳定的选择器、测试隔离、以用户为中心的测试和性能考虑。.
playwright
Playwright: e2e testing, page objects, fixtures, assertions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.