unit-test

A project command that runs the unit-testing stage for a specified feature or work item.

In plain words
What is it for?
Use it to run unit tests for an epic, create its test summary, and advance the configured development pipeline.
Why use it?
It follows the project's configured testing workflow instead of guessing which instructions, roles, or skills to use. It also records the test summary in the expected project document.

Command for Claude Code

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/aidlc-io/aidlc/unit-test
Clone the repo
git clone --depth 1 https://github.com/aidlc-io/aidlc

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 342 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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00342
Opus 5 $0.00014 $0.00171
Sonnet 5 $0.00005 $0.00068
Haiku 4.5 $0.00003 $0.00034

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

Security

Grade A, and why

unit-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 3d 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/unit-test.md · 24 lines

What it actually says

/unit-test — Unit Test

You were invoked as /unit-test <epic> with arguments: $ARGUMENTS (the epic id).

Run the unit-test phase for this epic by following the AIDLC dispatch procedure exactly as /aidlc <epic> unit-test would:

  1. Read docs/epics/<epic>/state.jsonpipelineId.
  2. In .aidlc/workspace.yaml, find that pipeline and its unit-test step (name/agent === unit-test). Use that step's agent + skills — never assume; two pipelines can wire unit-test differently.
  3. If the pipeline has no unit-test step, tell the user this epic's pipeline (<pipelineId>) has no unit-test phase, suggest /aidlc <epic> to run the next eligible phase, and stop.
  4. Otherwise load the persona (.claude/agents/<agent>.md) + skill(s) (.claude/skills/<skill>.md), adopt them (unless the active standard is none), then follow the structural contract: read state/inputs, write to docs/epics/<epic>/artifacts/UNIT-TEST-SUMMARY.md (or the step's declared artifact), and tell the user to click "Mark step done".
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. 3d ago First seen · 24 lines · 0 tokens per session scan A 990e644d3f7d

Subscribe to this mod's changes

unit-test is a command published in the GitHub repository aidlc-io/aidlc (58 stars, last pushed 29d ago), licensed MIT. It adds 27 tokens to every session and 342 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.