critical-path

critical-path is a command for Claude Code from ncklrs/claude-chrome-user-testing. It costs 26 tokens per session (2,013 once invoked), scanned A, original, MIT.

A test runner for essential user journeys, such as buying something or creating an account. A critical path is a task users must be able to complete for the product's main purpose to work.

In plain words
What is it for?
Use it to run all configured critical paths or one named path from a base URL. You can choose a fictional user, screen size, network condition, recordings, report format, and whether to post results to a GitHub pull request.
Why use it?
It checks the flows that matter most, so a failure in a core journey is found quickly and can optionally stop the remaining checks.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the user-testing-agent plugin — 14 skills, 10 commands shipped together

Install

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.

agentmods
npx agentmods add commands/ncklrs/claude-chrome-user-testing/critical-path
Clone the repo
git clone --depth 1 https://github.com/ncklrs/claude-chrome-user-testing

Made for: Claude Code.

Or install user-testing-agent, the plugin that ships this one along with the rest of its 14 skills, 10 commands.

Wrote 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.

agentmods badge for critical-path

README.md
[![agentmods](https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/critical-path.svg)](https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/critical-path)
Your own site
<a href="https://agentmods.dev/commands/ncklrs/claude-chrome-user-testing/critical-path"><img src="https://agentmods.dev/badge/commands/ncklrs/claude-chrome-user-testing/critical-path.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,013 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.02013
Opus 5 $0.00013 $0.01007
Sonnet 5 $0.00005 $0.00403
Haiku 4.5 $0.00003 $0.00201

Measured 6d ago against content hash 20ec995e7ac5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

critical-path 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 6d 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.

commands/critical-path.md · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Critical Path Command

Test must-work user journeys. Critical paths are essential flows that must always work - if they fail, users can't accomplish core tasks.

Arguments

Parse the following from $ARGUMENTS:

  • --url <url> (required): Base URL for testing
  • --path <name> (optional): Run specific path only (default: all paths)
  • --persona <id> (optional): Override default persona for all paths
  • --quiet (optional): Summary only output
  • --fail-fast (optional): Stop on first failure
  • --record (optional): Record sessions as Playwright Traces
  • --record-path <path> (optional): Custom trace output path
  • --viewport <mobile|tablet|desktop> (optional): Device viewport size (default: desktop)
  • --output <markdown|json> (optional): Report output format (default: markdown)
  • --network <slow-3g|fast-3g|offline> (optional): Network throttling preset
  • --pr <number> (optional): Post results as GitHub PR comment

Defining Critical Paths

Create .claude/critical-paths.json in your project:

{
  "paths": [
    {
      "name": "purchase-flow",
      "description": "Complete purchase from browse to confirmation",
      "persona": "impulse-buyer",
      "priority": "critical",
      "steps": [
        { "action": "navigate", "to": "/" },
        { "action": "task", "do": "find and select a product" },
        { "action": "task", "do": "add to cart" },
        { "action": "task", "do": "proceed to checkout" },
        { "action": "task", "do": "complete guest checkout" },
        { "action": "verify", "element": "order confirmation number" }
      ]
    },
    {
      "name": "account-creation",
      "description": "New user registration flow",
      "persona": "genz-digital-native",
      "priority": "critical",
      "steps": [
        { "action": "navigate", "to": "/signup" },
        { "action": "task", "do": "complete signup form" },
        { "action": "task", "do": "submit registration" },
        { "action": "verify", "element": "welcome message or dashboard" }
      ]
    },
    {
      "name": "password-reset",
      "description": "Password recovery flow",
      "persona": "boomer-tech-averse",
      "priority": "high",
      "steps": [
        { "action": "navigate", "to": "/login" },
        { "action": "task", "do": "find forgot password link" },
        { "action": "task", "do": "enter email address" },
        { "action": "task", "do": "submit reset request" },
        { "action": "verify", "element": "confirmation message" }
      ]
    }
  ]
}

Read the full file on GitHub · 304 lines

Changes

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.

  1. 6d ago First seen · 304 lines · 26 tokens per session scan A 20ec995e7ac5

Subscribe to this mod's changes

critical-path is a command published in the GitHub repository ncklrs/claude-chrome-user-testing (19 stars, last pushed 8mo ago), licensed MIT. It adds 26 tokens to every session and 2,013 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-30.