test

A repository test command that follows the project's documented testing workflow step by step.

In plain words
What is it for?
Running the relevant tests after code changes and reporting the exact commands and results.
Why use it?
It gives testing a consistent process and requires evidence of what was run. If tests cannot run, it records the blockers instead of hiding them.

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/kbwen/agent-virtual-office/test
Clone the repo
git clone --depth 1 https://github.com/KbWen/agent-virtual-office

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 79 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00000 $0.00079
Opus 5 $0.00000 $0.00039
Sonnet 5 $0.00000 $0.00016
Haiku 4.5 $0.00000 $0.00008

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

Security

Grade A, and why

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 2d 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

This is a copy

100% identical to test — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/test.md · 15 lines

What it actually says

/test

Execute the canonical workflow: .agent/workflows/test.md

Required reads before execution

  1. Active Work Log — must contain implementation evidence

Execution

Follow every step in .agent/workflows/test.md sequentially. Execute the minimal relevant test set and report commands + results. If tests cannot run, state blockers explicitly. End response with ⚡ ACX.

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. 2d ago First seen · 15 lines · 0 tokens per session scan A 7f7e8ad165c6

Subscribe to this mod's changes

test is a command published in the GitHub repository KbWen/agent-virtual-office (11 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 79 tokens. A static security scan graded it A with 0 findings. It is 100% identical to test, differing in 0 lines, and is treated as a copy.