A command for investigating and fixing failing automated tests. Test-driven analysis means using the failing test and repeatable test runs to determine whether the test or the code is wrong.

Use it with a test file, test name, or the whole suite to identify the failure, apply a fix, and verify that the fix works.

It provides a focused debugging process and repository-specific test commands, while avoiding test runs that can give misleading results.

test — Command for Claude Code by dork-labs/dorkos

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.

Clone the repo

git clone --depth 1 https://github.com/dork-labs/dorkos

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 41 skills, 44 commands, 5 agents, 4 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/dork-labs/dorkos/test/github.svg)](https://agentmods.dev/commands/dork-labs/dorkos/test)

Your own site

<a href="https://agentmods.dev/commands/dork-labs/dorkos/test"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/test/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/dork-labs/dorkos/test"><img src="https://agentmods.dev/badge/commands/dork-labs/dorkos/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 872 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00014	$0.00872
Opus 5.5	$0.00006	$0.00349
Sonnet 5.5	$0.00003	$0.00174
Haiku 4.5	$0.00001	$0.00087

Measured 1mo ago against content hash 2323836c64d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

.claude/commands/debug/test.md · 49 lines

How it starts

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

Test Failure Debugging

Debug and fix the failing test(s) described by $ARGUMENTS (a test file path, a test name pattern, or empty for the whole suite). Load the debugging-test-failures skill — it carries the methodology (read the failing test first, distinguish test bugs from implementation bugs, verify the fix would fail on wrong code). This command adds the project-specific ground truth below.

Running tests in this repo

pnpm vitest run <path-to-test-file>        # ONE test file — fastest loop (~1-2s)
pnpm vitest run <path> -t "test name"      # One test case within a file
pnpm vitest run apps/server/src/services   # Positional filter — a directory or substring
pnpm test -- --run                         # Full suite via Turborepo (single run, no watch)

Gotchas:

Never use bare pnpm vitest run for full runs — outside Turborepo it misses per-package env setup and falsely fails 2 tests in the dev environment. Full runs go through pnpm test -- --run. If a failure only reproduces under bare vitest, suspect this before suspecting the code.
Vitest filters are positional (path or name substrings after vitest run), plus -t for test-name patterns. --testPathPattern is a Jest flag and is invalid here.
Snapshot updates: pnpm vitest run <path> -u — only after confirming the change is intentional.
Stale @dorkos/shared dist after a pull causes false-red type errors in tests — rebuild with pnpm --filter @dorkos/shared build.

Project testing patterns

Full conventions: .claude/rules/testing.md and contributing/ testing guide. The essentials:

Tests live in __tests__/ alongside source; Vitest with vi.mock().
Client component tests: need /** @vitest-environment jsdom */, React Testing Library, and a mock Transport via TransportProvider (createMockTransport from @dorkos/test-utils). Missing jsdom directive or missing Transport wrapper are the two most common setup failures.
Server route tests: use FakeAgentRuntime + TestScenario from @dorkos/test-utils, never hand-rolled runtime mocks. If the AgentRuntime interface grew a method, FakeAgentRuntime tests fail to compile — that's intentional.
SSE integration tests: message POSTs are trigger-only 202s; collect frames from the durable stream with collectDurableEvents (@dorkos/test-utils) and always pass until for live streams.
SDK-level scenarios: builders in apps/server/src/services/runtimes/claude-code/__tests__/sdk-scenarios.ts — importable only inside services/runtimes/claude-code/ (ESLint SDK boundary).

Read the full file on GitHub · 49 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.

1mo ago First seen · 49 lines · 14 tokens per session scan A 2323836c64d6

Subscribe to this mod's changes

test is a command published in the GitHub repository dork-labs/dorkos (10 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 872 once invoked, about $0.0001 per session on Opus 5.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.

Autonomous Agents Claude Code Debugging TDD Testing agent-sdk ai-agents anthropic claude

test

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Test Failure Debugging

Running tests in this repo

Project testing patterns

What this file has done since we first saw it

Other commands, from other repositories

debug

pair

work-flow-bugfix

tdd

cpp-test

go-test