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 lubochka/xiigen-general-skills --skill user-journey-testinggit 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/skills/lubochka/xiigen-general-skills/user-journey-testing)<a href="https://agentmods.dev/skills/lubochka/xiigen-general-skills/user-journey-testing"><img src="https://agentmods.dev/badge/skills/lubochka/xiigen-general-skills/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/skills/lubochka/xiigen-general-skills/user-journey-testing"><img src="https://agentmods.dev/badge/skills/lubochka/xiigen-general-skills/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.00027 | $0.00187 |
| Opus 5 | $0.00014 | $0.00093 |
| Sonnet 5 | $0.00005 | $0.00037 |
| Haiku 4.5 | $0.00003 | $0.00019 |
Grade A, and why
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 11d 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.
- 11d ago First seen · 34 lines · 27 tokens per session scan A bc34c60eb8e8
user-journey-testing is a skill published in the GitHub repository lubochka/xiigen-general-skills (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 187 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-08-31.
Other skills, from other repositories
e2e-check
Run E2E tests or interactive browser verification. Triggers on: 'run e2e', 'e2e test', 'browser test', 'check in browser', 'verify UI', 'interactive test'.
pdlc-quality
A quality gate that runs configured coverage, end-to-end, and lint checks, compares their real results with declared targets, and creates a report for human approval.
test-health-check
Prove that a unit, integration, or end-to-end test genuinely guards its stated behavior by running a few targeted fault probes (reachability, sensitivity, oracle validity, reliability) around the code under test — instead of trusting coverage. Use during active test development or test review — after writing or…
setup-playwright
Use when adding, extending, or repairing a repo-owned Playwright test harness across Node Playwright Test, Playwright Pytest, or .NET/Java test frameworks. Also use when explicitly persisting @playwright/cli developer tooling, or adding or regenerating Playwright Test Agent definitions for a compatible Node Playwright…
playwright-testing
Use for explicitly requested live browser investigation with playwright-cli, or for writing, debugging, reviewing, or hardening Playwright tests in an existing working harness across Node, Python, .NET, or Java. Covers flake triage, locator refinement, visual and responsive checks, test structure, fixtures, auth-state…
pdlc-e2e
A workflow for creating and running end-to-end tests that follow a complete user journey through an application. End-to-end, or E2E, tests check several connected parts together, such as logging in, completing a task, and checking the result.