A test command that directs you to the appropriate kind of testing for a codebase or app. It covers unit tests, browser testing, quality checks, exploratory testing, visual comparisons, load tests, and mobile emulators.

Running tests on individual functions, live web flows, full applications, screenshots, performance under load, and native mobile builds.

It helps prevent choosing the wrong test method and provides a sequence for checking changes before committing them.

test — Command by kensaurus

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/kensaurus/cursor-kenji/test

Clone the repo

git clone --depth 1 https://github.com/kensaurus/cursor-kenji

Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 512 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.

Model	Per session	Once invoked
Fable 5	$0.00025	$0.00512
Opus 5	$0.00013	$0.00256
Sonnet 5	$0.00005	$0.00102
Haiku 4.5	$0.00003	$0.00051

Measured 2d ago against content hash 76a15e913571, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

test 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 2d 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/test.md · 29 lines

What it actually says

/test

Type check → lint → unit → integration → E2E → coverage. Verify quality before committing.

This command is a thin entry point. Pick the right skill for the target:

test-unit — write and improve unit tests (Jest, Vitest, pytest, Go test).
test-playwright — PDCA the changes you just made: drive the live app for the touched flows + blast radius and fix pain points as you go.
test-qa — full-app webapp QA, dynamic user stories, CRUD verification.
test-exploratory — unscripted monkey wander as GUEST then LOGGED-IN, then a guest-vs-authed diff. Discovery only — do not fix in-pass.
test-visual-regression — Playwright screenshot baselines and CI pixel diffs.
test-load — k6/Artillery throughput, latency percentiles, breaking point. Never hit prod unsigned.
mobile-emulator-test — native mobile builds (RN/Expo/Capacitor/Flutter) on Android emulator.

All browser QA is manual and headed. Drive a visible browser through playwright-cli (npx --yes @playwright/cli@latest -s=<session> …, with --headed on open) one real user action at a time — never *.spec.ts, npx playwright test, or driving the UI through eval/run-code. First read the protocol-browser-anti-stall skill (Rule 0).

Use /test to explicitly trigger testing. Otherwise, say "test this", "test my changes with playwright", "write tests", "QA the app", "monkey test the app", "guest vs logged in", "add visual regression tests", "load test this", or "smoke-test on emulator" and the appropriate skill auto-fires.

Highest-impact combo: test-exploratory → workflow-feedback-to-closure → test-playwright (wander twice → ticket real bugs → lock the worst ones). Pre-release: wander first, then workflow-quality-gate.

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.

2d ago First seen · 29 lines · 25 tokens per session scan A 76a15e913571

Subscribe to this mod's changes

test is a command published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 4d ago), licensed MIT. It adds 25 tokens to every session and 512 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.

Browser automation Mobile Testing agent-skills ai-agent claude cursor cursor-ai cursor-ide

test

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

/test

What this file has done since we first saw it

Other commands, from other repositories

commit-msg

code-review

prp-new

boot

clean

context