A test workflow supporting normal test runs and test-driven development, or TDD—the practice of writing a failing test before the code that makes it pass.

Use it to run all tests, select tests by pattern, review coverage, or work through the RED-GREEN-REFACTOR cycle.

It organizes testing, coverage checks, and the TDD cycle so expected behavior and regressions are easier to verify.

test — Command for Claude Code by stefan-jansen/claude-code-toolkit

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/stefan-jansen/claude-code-toolkit

Made for: Claude Code.

Or install development, the plugin that ships this one along with the rest of its 7 commands, 3 agents.

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/stefan-jansen/claude-code-toolkit/test/github.svg)](https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/test)

Your own site

<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/test"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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/stefan-jansen/claude-code-toolkit/test"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 416 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.00009	$0.00416
Opus 5.5	$0.00004	$0.00166
Sonnet 5.5	$0.00002	$0.00083
Haiku 4.5	$0.00001	$0.00042

Measured 1mo ago against content hash 820a5398c18f, 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.

plugins/development/commands/test.md · 69 lines

What it actually says

Test Workflow

Input: $ARGUMENTS

Usage

/test             # Run full test suite with coverage
/test tdd         # TDD workflow: RED-GREEN-REFACTOR
/test auth        # Run tests matching pattern
/test coverage    # Coverage analysis only

Process

1. Determine Mode

tdd: Full Test-Driven Development cycle
pattern: Run matching tests only
No args: Full suite with coverage analysis

2. Detect Framework

Python: pytest, unittest
JavaScript: Jest, Mocha
Go: built-in testing
Check config files for settings

3. TDD Mode (via test-engineer agent)

RED: Write failing tests defining expected behavior

Include edge cases, error conditions, boundary values
Verify meaningful failure messages

GREEN: Minimal implementation to pass tests

Simplest code possible
Only what's needed for current tests

REFACTOR: Improve while keeping green

Structure, readability, performance
Documentation and type hints

VALIDATE: Quality assurance

Full suite regression check
Coverage ≥80% threshold

4. Standard Test Execution

Run tests (all or filtered by pattern)
Collect coverage data
Parse results for failures/skips
Report coverage by module

5. Results Analysis

Coverage: line, branch, function percentages
Gaps: uncovered code paths
Quality: organization, naming, maintainability
Performance: execution time

Success Criteria

✅ All tests pass
✅ Coverage ≥80%
✅ Clear failure messages
✅ Reasonable execution time
✅ Tests are maintainable

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 · 69 lines · 9 tokens per session scan A 820a5398c18f

Subscribe to this mod's changes

test is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 416 once invoked, about $0.0000 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-30.

Claude Code TDD Testing agents anthropic coding-agents framework plugins

test