test-plan

test-plan is a command for Claude Code from travisjneuman/.claude. It costs 20 tokens per session (2,473 once invoked), scanned A, original, MIT.

A command that examines a project and creates a test strategy document with a test matrix, coverage goals, and a test-pyramid plan.

In plain words
What is it for?
Use it when planning tests for Node.js, Python, Go, or Rust projects, including projects using tools such as Jest, Vitest, Pytest, Playwright, or Cypress.
Why use it?
It turns a codebase's structure and existing test setup into a written plan for deciding what to test and how much.

Command for Claude Code

Written for Claude Code: arguments in frontmatter.

Good fit Use it when planning tests for Node.js, Python, Go, or Rust projects, including projects using tools such as Jest, Vitest, Pytest, Playwright, or Cypress.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/travisjneuman/.claude/test-plan
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/travisjneuman/.claude

Made for: Claude Code.

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 test-plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/travisjneuman/.claude/test-plan/github.svg)](https://agentmods.dev/commands/travisjneuman/.claude/test-plan)
Your own site
<a href="https://agentmods.dev/commands/travisjneuman/.claude/test-plan"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/test-plan/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.

agentmods 80×15 button for test-plan

Your own site · 80×15
<a href="https://agentmods.dev/commands/travisjneuman/.claude/test-plan"><img src="https://agentmods.dev/badge/commands/travisjneuman/.claude/test-plan.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 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,473 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00020 $0.02473
Opus 5 $0.00010 $0.01236
Sonnet 5 $0.00004 $0.00495
Haiku 4.5 $0.00002 $0.00247

Measured 7d ago against content hash ef70c6b3b0b1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

test-plan 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 7d 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-plan.md · 358 lines

How it starts

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

Test Plan Generator

Analyzes the current project structure and generates a comprehensive test strategy document with test matrix, coverage goals, and test pyramid allocation.

Usage

/test-plan [focus]

Execution Protocol

Step 1: Project Discovery

Analyze the current project to understand the tech stack and structure:

Detect framework and tooling:

# Check for package.json (Node/JS/TS projects)
[ -f package.json ] && cat package.json | head -50

# Check for pyproject.toml or requirements.txt (Python projects)
[ -f pyproject.toml ] && cat pyproject.toml | head -30
[ -f requirements.txt ] && head -20 requirements.txt

# Check for go.mod (Go projects)
[ -f go.mod ] && cat go.mod | head -10

# Check for Cargo.toml (Rust projects)
[ -f Cargo.toml ] && cat Cargo.toml | head -20

Detect existing test infrastructure:

# Existing test files
find . -name "*.test.*" -o -name "*.spec.*" -o -name "*_test.*" -o -name "test_*" | head -30

# Test config files
ls jest.config* vitest.config* pytest.ini setup.cfg .mocharc* playwright.config* cypress.config* 2>/dev/null

# Test directories
ls -d test/ tests/ __tests__/ e2e/ integration/ 2>/dev/null

Detect project structure:

# Source directories and top-level modules
find . -maxdepth 3 -type d -not -path "*/node_modules/*" -not -path "*/.git/*" -not -path "*/dist/*" -not -path "*/.next/*" -not -path "*/__pycache__/*" | head -40

If {{focus}} is provided, narrow discovery to that area only.


Step 2: Identify Testable Components

Based on project discovery, categorize components into testable units:

Component Type Examples Primary Test Level
Pure functions/utilities Formatters, validators, helpers, parsers Unit
Data models/types Database models, schemas, DTOs Unit
Business logic/services Service classes, use cases, domain logic Unit + Integration
API endpoints/routes REST handlers, GraphQL resolvers Integration
UI components React components, Vue components, Svelte components Unit (render) + Integration
Database operations Repositories, queries, migrations Integration
External integrations API clients, email, payment, auth providers Integration (mocked)
User workflows Login flow, checkout, onboarding E2E
Configuration Env validation, feature flags, startup Unit

Read the full file on GitHub · 358 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. 7d ago First seen · 358 lines · 20 tokens per session scan A ef70c6b3b0b1

Subscribe to this mod's changes

test-plan is a command published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 2,473 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-09-03.