A test-running command that detects whether a project uses Jest, Vitest, Playwright, or Cypress, then runs the relevant tests. Tests are checks that verify code behaves as expected.

Use it to run unit, integration, or end-to-end tests, optionally in watch mode or with coverage, and review failures and results.

It removes the need to remember the right test command and helps narrow runs to relevant files or changes.

ts-test — Command by andronics

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/andronics/claude-plugin-typescript-pro/ts-test

Clone the repo

git clone --depth 1 https://github.com/andronics/claude-plugin-typescript-pro

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

When invoked 554 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.00019	$0.00554
Opus 5	$0.00010	$0.00277
Sonnet 5	$0.00004	$0.00111
Haiku 4.5	$0.00002	$0.00055

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

Security

Grade A, and why

ts-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/ts-test.md · 64 lines

What it actually says

Run TypeScript tests with automatic framework detection and intelligent filtering:

Detect Test Framework
- Check package.json for test dependencies
- Look for config files: vitest.config.ts, jest.config.ts, playwright.config.ts
- Identify: Vitest, Jest, Playwright, Cypress, or multiple frameworks
- Determine if this is unit, integration, or E2E test request
Determine Test Scope
- If $ARGUMENTS provided, use as test pattern/filter
- If no arguments, detect from context:
  - Recent file changes (git status)
  - Files mentioned in conversation
  - All tests (default)
- Determine test type: unit, integration, or e2e
Run Appropriate Tests
- Vitest: npx vitest run $ARGUMENTS
- Jest: npx jest $ARGUMENTS
- Playwright: npx playwright test $ARGUMENTS
- Cypress: npx cypress run --spec $ARGUMENTS
- Use watch mode if explicitly requested
- Generate coverage if --coverage flag detected
Analyze Results
- Parse test output for failures
- Count: passed, failed, skipped tests
- Show code coverage summary if available
- Identify flaky tests (if using Playwright)
Handle Failures
- For each failing test:
  - Show test name and error message
  - Display code snippet where failure occurred
  - Show expected vs actual values
  - Suggest potential fixes based on error type
Type-Related Test Failures
- Identify test failures caused by type issues
- Suggest fixing type definitions vs test assertions
- Check for type assertion issues in test code
Performance Analysis
- Show slowest tests if runtime > 1s
- Suggest optimizations for slow tests
- Recommend parallelization if appropriate
Next Steps
- If all tests pass: celebrate and show coverage
- If tests fail: offer to fix failing tests
- Suggest adding tests for untested code
- Recommend running type-check separately if not done

Examples:

/ts-test - Run all tests
/ts-test user - Run tests matching "user"
/ts-test --watch - Run in watch mode
/ts-test --coverage - Generate coverage report

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 · 64 lines · 19 tokens per session scan A 87901c3a82ba

Subscribe to this mod's changes

ts-test is a command published in the GitHub repository andronics/claude-plugin-typescript-pro (4 stars, last pushed 10mo ago), licensed MIT. It adds 19 tokens to every session and 554 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 Code review Testing

ts-test

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

auto-browse

research-perplexity

webapp-testing

review

graphify

laravel-playwright