A test-writing command that examines recently changed or specified code and adds tests following the project's conventions. Tests are checks that confirm code behaves as expected.

Use it after changing code or when a target lacks tests. It detects common test setups, writes coverage for expected and unusual inputs, and runs the tests.

It reduces the work of finding the right test files and identifying normal cases, edge cases, and errors to cover.

add-tests — Command for coding agents by CloudAI-X: A test-writing command that examines recently changed or specified…

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/cloudai-x/claude-workflow-v2/add-tests

Clone the repo

git clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2

Or install claude-workflow-v2, the plugin that ships this one along with the rest of its 14 skills, 26 commands, 7 agents, 6 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/cloudai-x/claude-workflow-v2/add-tests.svg)](https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/add-tests)

Your own site

<a href="https://agentmods.dev/commands/cloudai-x/claude-workflow-v2/add-tests"><img src="https://agentmods.dev/badge/commands/cloudai-x/claude-workflow-v2/add-tests.svg" alt="Measured on agentmods" 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 384 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.00009	$0.00384
Opus 5	$0.00005	$0.00192
Sonnet 5	$0.00002	$0.00077
Haiku 4.5	$0.00001	$0.00038

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

Security

Grade A, and why

add-tests 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 4d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

add-tests — 100% identical, 0 lines differ

commands/add-tests.md · 33 lines

What it actually says

Context

Recently modified files: !git diff --name-only HEAD~3 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go|rs)$' | head -10 || echo "No recent changes"
Test framework detection: !cat package.json 2>/dev/null | grep -E '"(jest|vitest|mocha)"' | head -1 || ls pytest.ini pyproject.toml 2>/dev/null | head -1 || echo "Unknown test framework"
Existing test files: !find . -name "*test*" -o -name "*spec*" 2>/dev/null | grep -E '\.(ts|tsx|js|jsx|py|go)$' | head -10 || echo "No test files found"
Test directory structure: !ls -la tests/ test/ __tests__/ spec/ 2>/dev/null | head -20 || echo "No standard test directory"

Task

Add tests for the specified target:

Identify the file/function to test
Find the corresponding test file (or create one following project conventions)
Analyze the code to understand:
- Input/output behavior
- Edge cases
- Error conditions
Write comprehensive tests covering:
- Happy path
- Edge cases
- Error handling
Run the tests to verify they pass

Target: $ARGUMENTS

If no target specified, focus on recently modified files that lack test coverage.

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.

4d ago First seen · 33 lines · 9 tokens per session scan A b2f854ff9f37

Subscribe to this mod's changes

add-tests is a command published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 10d ago), licensed MIT. It adds 9 tokens to every session and 384 once invoked, about $0.0000 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-30.

Testing agent-skills ai ai-agents claude-code codex cursor

add-tests

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

What it actually says

Context

Task

What this file has done since we first saw it

Other commands, from other repositories

upgrade

release

add-agent

migrate

lians-recall

t800-onboard