Borrowing it
Nothing to install: this file belongs to aidlc-io/aidlc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aidlc-io/aidlc/main/.claude/commands/unit-test.mdgit clone --depth 1 https://github.com/aidlc-io/aidlcWrote 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.
[](https://agentmods.dev/commands/aidlc-io/aidlc/unit-test)<a href="https://agentmods.dev/commands/aidlc-io/aidlc/unit-test"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/unit-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.
<a href="https://agentmods.dev/commands/aidlc-io/aidlc/unit-test"><img src="https://agentmods.dev/badge/commands/aidlc-io/aidlc/unit-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00027 | $0.00342 |
| Opus 5.5 | $0.00011 | $0.00137 |
| Sonnet 5.5 | $0.00005 | $0.00068 |
| Haiku 4.5 | $0.00003 | $0.00034 |
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 2mo 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.
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:
- Read
docs/epics/<epic>/state.json→pipelineId. - In
.aidlc/workspace.yaml, find that pipeline and itsunit-teststep (name/agent===unit-test). Use that step'sagent+skills— never assume; two pipelines can wireunit-testdifferently. - If the pipeline has no
unit-teststep, tell the user this epic's pipeline (<pipelineId>) has nounit-testphase, suggest/aidlc <epic>to run the next eligible phase, and stop. - Otherwise load the persona (
.claude/agents/<agent>.md) + skill(s) (.claude/skills/<skill>.md), adopt them (unless the active standard isnone), then follow the structural contract: read state/inputs, write todocs/epics/<epic>/artifacts/UNIT-TEST-SUMMARY.md(or the step's declared artifact), and tell the user to click "Mark step done".
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.
- 2mo ago First seen · 24 lines · 0 tokens per session scan A 990e644d3f7d
unit-test is a command published in the GitHub repository aidlc-io/aidlc (65 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 342 once invoked, about $0.0001 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.
Other commands, from other repositories
session
Complete guide to managing pair programming sessions.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
lg:node
Create, modify, and manage nodes in LangGraph graphs including LLM nodes, tool nodes, human-in-the-loop, subgraphs, and conditional nodes.
test-audit
Writes a versioned TESTAUDIT.md; with --fix, quarantines the rot in gated, revertible commits. TRIGGER WHEN: auditing a test suite, measuring test health, finding dead or flaky or redundant tests, or diagnosing failure causes and proposing temporary quarantine. DO NOT TRIGGER WHEN: one module's tests are consolidated…
story-and-test
For the component(s) in scope.