A command that creates a focused plan for testing the current coding task.

Use it to decide which tests or verification steps to run after making a code change.

It helps identify the smallest checks needed to catch problems before spending time on a larger test run.

test-plan — Command by smallcloudai

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/smallcloudai/refact/test-plan

Clone the repo

git clone --depth 1 https://github.com/smallcloudai/refact

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

When invoked 41 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.00010	$0.00041
Opus 5	$0.00005	$0.00020
Sonnet 5	$0.00002	$0.00008
Haiku 4.5	$0.00001	$0.00004

Measured yesterday against content hash 48dc7ccfc93b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

refact-agent/engine/src/yaml_configs/marketplace/commands/test-plan.md · 8 lines

What it actually says

Create a focused test plan for the current task, including the smallest useful checks first.

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.

yesterday First seen · 8 lines · 10 tokens per session scan A 48dc7ccfc93b

Subscribe to this mod's changes

test-plan is a command published in the GitHub repository smallcloudai/refact (3,540 stars, last pushed 3mo ago), licensed BSD-3-Clause. It adds 10 tokens to every session and 41 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-30.

Data and AI Planning RAG Testing developer-tools fine-tuning open-source self-hosted vscode

test-plan

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

pipi_setup

triage

loci-scan

card

tree

requirement-review