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.
git clone --depth 1 https://github.com/lubochka/xiigen-general-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/rules/lubochka/xiigen-general-skills/xiigen-user-journey-testing)<a href="https://agentmods.dev/rules/lubochka/xiigen-general-skills/xiigen-user-journey-testing"><img src="https://agentmods.dev/badge/rules/lubochka/xiigen-general-skills/xiigen-user-journey-testing/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/rules/lubochka/xiigen-general-skills/xiigen-user-journey-testing"><img src="https://agentmods.dev/badge/rules/lubochka/xiigen-general-skills/xiigen-user-journey-testing.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.00000 | $0.00190 |
| Opus 5.5 | $0.00000 | $0.00076 |
| Sonnet 5.5 | $0.00000 | $0.00038 |
| Haiku 4.5 | $0.00000 | $0.00019 |
Grade A, and why
xiigen-user-journey-testing 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
User Journey Testing
Purpose
Validate work through a realistic user path.
When to Use
Use for UX, tool workflows, onboarding, and generated instructions.
Inputs
User goal, steps, expected result, viewport/tool/runtime context.
Steps
- State the user's goal.
- Walk the end-to-end steps.
- Record friction, failure, or confusion.
- Update instructions or mark blockers.
Gates
The journey either succeeds or has a clear blocker and next action.
Evidence
Journey notes, screenshots when safe, command output, or report.
Anti-Patterns
Testing only implementation internals and ignoring the user outcome.
Related
e2e-test-matrix, output-readability-gate
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 · 35 lines · 0 tokens per session scan A d2654d32f708
xiigen-user-journey-testing is a cursor rule published in the GitHub repository lubochka/xiigen-general-skills (1 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 190 tokens. 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 cursor rules, from other repositories
gemini_qa_loop
Continuous dogfood loop using Gemini 3 Flash vision to score and fix UI/UX issues automatically.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
playwright-ops-demo
Agent rules for playwright-ops-demo.
browser-ops-demo
Agent rules for browser-ops-demo.
qa-engineer
QA & Test Automation Engineer.